Data communication

ABSTRACT

A telephony user device capable of establishing a communications session for communication of data with respect to at least one other device in a data communications network, the telephony user device being adapted to provide a reconfigurable graphical user interface, establish a telephone call with a service provider, establish a separate communications session, separate from the telephone call, for the transfer of data to/from the at least one other device, on the basis of one or more call party details associated with the telephone call, and reconfigure at least a first part of the graphical user interface according to configuration data determined by the service provider and received in the separate communication session.

CROSS REFERENCE TO PRIOR APPLICATIONS

This application is a continuation of International Application No.PCT/PCT/GB2012/050335, filed Feb. 14, 2012 and designating the U.S.,which claims priority to Great Britain Patent Application No. GB1104623.2, filed Mar. 18, 2011, which also claims priority to the U.S.Patent Application No. 61/442,773 filed Feb. 14, 2011 all of which areincorporated herein by reference in their entirety.

TECHNICAL FIELD

The present disclosure relates to the communication of data. Inparticular, but not exclusively, the present disclosure relates to thecommunication of data between user devices during telephone calls.

BACKGROUND

Communication between parties in a telecommunications network can becarried out in a number of ways. Most commonly, communication is carriedout by a calling party dialing the telephone dialing number of a calledparty telephony device on a calling party telephony device. The dialingof the telephone number causes a call set-up process to be carried outin the network which results in the telephone of the called partyringing. If the called party chooses to answer their telephone, atelephone call can ensue between the calling party and the called party.The telephone call allows audio data such as speech data to betransferred along an audio channel created between the calling partytelephony device and the called party telephony device.

Some telephony devices have enhanced capabilities which allow transferof video data along a video channel created between the calling partytelephone and the called party telephone. A video call may not bepossible unless both the calling and called party telephone devicessupport video call functionality.

Audio or video conferencing may be carried out between three or moreremote telephony devices, allowing communication of audio and/or videodata between parties to the conference.

Web conferencing is also possible between multiple remote parties usingdevices with combined data processing, display and telephonycapabilities. Web conferencing allows online meetings to be conductedfor viewing and/or collaborating on common multimedia content.

Parties may also exchange text data by use of text messaging servicessuch as the Short Message Service (SMS). Enhanced messaging servicessuch as the Multimedia Messaging Service (MMS) allow parties to exchangeimage and video data in addition to text data.

The example methods of communication described above provide a widerange of ways for remote parties to communicate with each other.However, each method typically has different requirements in terms ofdevice and/or network capability and interchanging between the differentmethods is either not possible or requires use of inconvenient set-up orconfiguration processes.

It would therefore be desirable to provide improved methods forcommunicating data between remote parties, including communication ofdata in a manner convenient to the parties.

SUMMARY

In accordance with first embodiments, there is a telephony user devicecapable of establishing a communications session for communication ofdata with respect to at least one other device in a data communicationsnetwork, the telephony user device comprising a processing systemconfigured to:

provide a reconfigurable graphical user interface;

establish a telephone call with a service provider;

establish a separate communications session, separate from the telephonecall, for the transfer of data to/from the at least one other device, onthe basis of one or more call party details associated with thetelephone call; and

reconfigure at least a first part of the graphical user interfaceaccording to configuration data determined by the service provider andreceived in the separate communication session,

wherein said reconfigurable graphical user interface comprises atouch-screen user interface, and

wherein said reconfiguration comprises configuring one or moretouch-sensitive screen regions in said at least first part which areoperable to initiate one or more operations of the telephony user devicein response to user input via the one or more touch-sensitive screenregions.

In accordance with second embodiments, there is apparatus adapted toestablish a communications session for communication of data withrespect to a telephony user device having a reconfigurable graphicaluser interface and at least one other device in a data communicationsnetwork, the apparatus comprising a processing system configured to:

receive call party details for a telephone call between the telephonyuser device and a service provider;

establish a separate communications session, separate from the telephonecall, for the transfer of data to/from the telephony user device and theat least one other device, on the basis of one or more call partydetails associated with the telephone call; and

transmit to the telephony user device, via the separate communicationsession, configuration data determined by the service provider, theconfiguration data being operable to instruct the telephony user deviceto reconfigure at least a part of the reconfigurable graphical userinterface,

wherein said reconfigurable graphical user interface comprises atouch-screen user interface, and

wherein said configuration data is operable to instruct said telephonyuser device to configure one or more touch-sensitive screen regions insaid at least first part which are operable to initiate one or moreoperations of the telephony user device in response to user input viathe one or more touch-sensitive screen regions.

In accordance with third embodiments, there is a service provider systemcapable of establishing a communications session for communication ofdata with respect to at least a first telephony user device in a datacommunications network, the system comprising:

a service management part adapted to manage service data for the serviceprovider;

a service data store adapted to store the service data;

a telephony part adapted to conduct a telephone call with a customer ofthe service provider via the at least first telephony user device; and

a data communications part adapted to:

-   -   establish a separate communications session, separate from the        telephone call, for the transfer of data to/from the first        telephony user device, on the basis of one or more call party        details associated with the telephone call; and

retrieve service data from the service data store and transmit dataincluding or derived from the retrieved service data via the session,

wherein said first telephony user device comprises a reconfigurablegraphical user interface having a touch-screen user interface, and

wherein said data including or derived from said retrieved service datawhich is transmitted via said session comprises configuration data whichis operable to instruct said telephony user device to configure one ormore touch-sensitive screen regions which are operable to initiate oneor more operations of the telephony user device in response to userinput via the one or more touch-sensitive screen regions.

In accordance with fourth embodiments, there is provided a computerprogram product comprising a non-transitory computer-readable storagemedium having computer readable instructions stored thereon, thecomputer readable instructions being executable by a computerized deviceto cause the computerized device to operate a telephony device accordingto the first, second or third embodiments.

Further features of embodiments will become apparent from the followingdescription of preferred embodiments, given by way of example only,which is made with reference to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system diagram according to embodiments.

FIG. 2 is a flow diagram depicting operation of embodiments using thesystem of FIG. 1.

FIG. 3 is a flow diagram depicting operation of embodiments using thesystem of FIG. 1.

FIG. 4 is a system diagram according to embodiments.

FIG. 5 is a flow diagram depicting operation of embodiments using thesystem of FIG. 4.

FIG. 6 is a flow diagram depicting operation of embodiments using thesystem of FIG. 4.

FIG. 7 is a system diagram according to embodiments.

FIG. 8 is a flow diagram depicting operation of embodiments using thesystem of FIG. 7.

FIG. 9 is a system diagram according to embodiments.

FIG. 10 is a flow diagram depicting operation of embodiments using thesystem of FIG. 9.

FIG. 11 is a flow diagram depicting operation of embodiments using thesystem of FIG. 9.

FIG. 12 is a system diagram according to embodiments.

FIG. 13 is a flow diagram depicting operation of embodiments using thesystem of FIG. 12.

FIG. 14 is a flow diagram depicting operation of embodiments using thesystem of FIG. 12.

FIG. 15 is a flow diagram depicting operation of embodiments using thesystem of FIG. 12.

FIG. 16 is a system diagram according to embodiments.

FIG. 17 is a flow diagram depicting operation of embodiments using thesystem of FIG. 16.

FIG. 18 is a flow diagram depicting operation of embodiments using thesystem of FIG. 16.

FIG. 19 is a flow diagram depicting operation of embodiments using thesystem of FIG. 16.

FIG. 20 shows a front view of a mobile telephony device according toembodiments.

FIG. 21 shows a front view of a mobile telephony device according toembodiments.

FIG. 22 shows a front view of a mobile telephony device according toembodiments.

DETAILED DESCRIPTION

FIG. 1 is a system diagram showing a data communications networkaccording to embodiments of the present disclosure. These embodimentsinvolve two mobile stations (MS) MS A and MS B which access public landmobile networks (PLMNs) PLMN A and PLMN B respectively via radiointerfaces. MS A and MS B may be smart phones having data processingcapabilities and operating systems.

PLMN A and PLMN B contain mobile telephony network infrastructureincluding one or more mobile switching centers, one or more base stationcontrollers, and one or more base transceiver stations; the function ofsuch entities is well known in the art and will not be described indetail here.

PLMN A and PLMN B are connected via a telecommunications network 104comprising one or more Public Switched Telephone Networks (PSTNs) and/orpacket networks. Telecommunications network 104 comprises one or moremedia and/or signaling gateway entities (not shown) for performingconversion between the various protocols and data formats used totransfer media and signaling data within and between the differentnetworks. Server (or server system) 100 has an associated data store 102and is connected to telecommunications network 104 via a packet network106. Although server 100 is depicted as a single entity in FIG. 1,server 100 may be a single device, a cluster of servers or serversforming a server system which is distributed throughout the datacommunications network.

MS A has an associated identity in the form of a telephone dialingnumber (TDN), TDN A. MS B has an associated identity in the form of atelephone dialing number TDN B. MS A has communication sessionapplication software running on it with an associated applicationidentifier AppID A. MS B also has communication session applicationsoftware running on it with an associated application identifier AppIDB.

In some embodiments, during installation of the application software onMS A, server 100 may be informed of AppID A and creates a record for MSA in data store 102 containing AppID A stored in association with TDN A.Similarly, in some embodiments, during installation of the applicationsoftware on MS B, server 100 may informed of AppID B and creates arecord for MS B in data store 102 containing AppID B stored inassociation with TDN B.

FIG. 2 is a flow diagram depicting operation of embodiments, for exampleimplemented in a system depicted in FIG. 1.

In this and subsequent flow diagrams, solid arrows denote transfer ofcontrol, messaging or signaling data, whereas dashed arrows denotetransfer of media or payload data.

A voice call is currently in progress between MS A in PLMN A and MS B inPLMN B, as shown by item 110. The voice call will typically be acircuit-switched voice call, the set-up and control for which is knownin the art.

Application software running on MS A detects that there is a call inprogress between MS A and MS B and notifies server 100 of call partydetails for the call, e.g. the TDNs of telephones involved in the call,TDN A associated with MS A and TDN B associated with MS B, in step 2 a.Similarly, application software running on MS B detects the call inprogress between MS B and MS A and notifies server 100 of call partydetails for the call, e.g. the TDNs of telephones involved in the call,TDN A associated with MS A and TDN B associated with MS B, in step 2 b.

Application software running on MS A may detect that the call is inprogress by registering with the operating system of MS A to be notifiedupon start of a call involving MS A. This could for example involveregistering with an application programming interface (API) of theoperating system of MS A associated with start and end of call events. Asimilar call detection process may occur on MS B.

In these embodiments, the user of MS A could be the calling or thecalled party for the call. Call party details are received from bothtelephony apparatus acting on behalf of the calling party and telephonyapparatus acting on behalf of the called party for the call, e.g.telephony device MS A and telephony device MS B.

Server 100 identifies that the notification of step 2 a from MS A andnotification of step 2 b from MS B have call party details, TDN A andTDN B, in common and establishes a separate communications session,separate from the telephone call, for the communication of data betweenMS A and MS B. The separate communications session is established on thebasis of the received call party details, TDN A and TDN B. The separatecommunications session is established whilst the telephone call is inprogress, and is continued in parallel with the telephone call, suchthat voice call data is transmitted via the telephone call and otherdata may be transmitted via the communications session, after theestablishment of the separate communications session.

Server 100 updates the records for MS A and MS B in data store 102 toindicate that a call is in progress between MS A and MS B and that acommunications session between MS A and MS B, separate to the voice callbetween MS A and MS B, has been established in step 2 c.

Server 100 may respond (not shown) to the notifications of steps 2 a and2 b by responding with respective acknowledgements to MS A and MS B.

If MS A wants to communicate data to (e.g. share data with) MS B, ittransmits the data to server 100 in step 2 d. Server 100 performs alookup in data store 102 using TDN A for MS A in step 2 e and identifiesthat a communications session has been established between MS A and MSB. Server 100 retrieves TDN B for MS B in step 2 f and transmits thedata received from MS A to MS B using the retrieved TDN B in step 2 g.

In embodiments, the lookup in data store 102 of step 2 e may also resultin AppID B being retrieved. The data may then be transmitted to MS Busing both TDN B and AppID B, with TDN B being used to locate MS B andAppID B being used to direct the data to the communications sessionapplication software running on MS B. The data may be transmitted bymeans of a push notification directed to AppID B of the communicationsession application on MS B. In the case of MS B being an Apple®iPhone®, the push notification could employ use of the Apple® PushNotification Service (APNS).

If MS B wants to send data to MS A, it sends the data to server 100 instep 2 h. Server 100 performs a lookup in data store 102 using TDN B forMS B in step 2 i and identifies that a communications session has beenestablished between MS B and MS A. Server 100 retrieves TDN A for MS Ain step 2 j and transmits the data received from MS B to MS A using theretrieved TDN A in step 2 k.

In embodiments, the lookup in data store 102 of step 2 j may also resultin AppID A being retrieved. The data may then be transmitted to MS Ausing both TDN A and AppID A, with TDN A being used to locate MS A andAppID A being used to direct the data to the communications sessionapplication software running on MS A. The data may be transmitted bymeans of a push notification directed to AppID A of the communicationsession application on MS A.

In embodiments, the communication session is established in the form ofa client-server relationship, with server 100 acting as the server andeach of MS A and MS B acting as clients. One connection is createdbetween server 100 and MS A and another connection is created betweenserver 100 and MS B. The two connections together create a channelbetween MS A and MS B through which data can be communicated in eitherdirection.

In embodiments, server 100 establishes client-server connections with MSA and MS B in response to receiving one or more client-server connectionrequests.

In embodiments, a client-server connection request is transmitted inresponse to the telephone call being established between MS A and MS B.In other embodiments, a client-server connection request is transmittedin response to initiation of a data communications service on MS A or MSB after the telephone call is established between them.

Each of the connections could be HyperText Transfer Protocol (HTTP) orHyperText Transfer Protocol Secure (HTTPS) connections.

To avoid loss of the channel between MS and MS B, the connections can bemaintained by maintenance messages (‘heartbeats’) transmitted fromserver 100 to MS A and MS B, for example transmitted at periodicintervals sufficiently short to prevent time-out of the connections dueto inactivity, e.g. a client-server connection can be maintained bytransmitting a message to keep the connection alive if the telephonecall lasts more than a connection threshold period.

The data communicated via the session may comprise server 100 receivingdata identifying a downloadable resource, selected from the groupconsisting of a photographic image data file; a word processing documentdata file; a spreadsheet document data file; a presentation documentdata file; a video image data file; and streaming video, from one of MSA and MS B, during the separate communications session, and transmittingthe data to the other of MS A and MS B, for example via theclient-server connection.

In embodiments, the communications session between MS A and MS B can bemaintained after the voice call is terminated allowing the users of MS Aand MS B to continue communicating data between their user devices.

In alternative embodiments, the separate communications session isestablished via server 100 and data is transmitted via a datacommunication path between MS A and MS B which is established on thebasis of information received from said server, but with server 100 notbeing including in the data communication path.

Server 100 may receive a service data object from MS A or MS B duringthe separate communications session and transmit the service data objectto the other of MS A and MS B.

Server 100 may receive a service data object from MS A or MS B duringthe separate communications session, process the service data object incombination with additional service data to generate derived servicedata; and transmit the derived service data to the other of MS A and MSB.

FIG. 3 is a flow diagram depicting operation of embodiments, for exampleimplemented in a system depicted in FIG. 1. Similarly to FIG. 2described above, a voice call is currently in progress between MS A inPLMN A and MS B in PLMN B, as shown by item 110.

Application software running on MS A detects that there is a call inprogress between MS A and MS B and notifies server 100 of call partydetails for the call, e.g. the TDNs of telephones involved in the call,TDN A associated with MS A and TDN B associated with MS B, in step 3 a.Here, however, MS B does not have application software or any othercapability which can detect the call with MS A and notify server 100 ofsuch. Instead, server 100 notifies MS B of the receipt of call partydetails for the call from MS A by transmitting a separate communicationsession initiation request to MS B in step 3 b. The communicationsession initiation request may cause a message such as “Do you want toestablish a data communication session with the party you are speakingto?” or such like. If the user of MS B accepts the request byappropriate user input, MS B transmits a separate communication sessioninitiation response to server 100 in step 3 c indicating that acommunication session between MS B and MS A, separate to the voice call,should be established.

In these embodiments, the user of MS A could be the calling or thecalled party for the call. Call party details are received from eithertelephony apparatus acting on behalf of the calling party or telephonyapparatus acting on behalf of the called party, e.g. MS A.

Once, the response of step 3 c is received, server 100 updates therecords for MS A and MS B in data store 102 in step 3 d to indicate thata call is in progress between MS A and MS B and that a separatecommunications session between MS A and MS B should be established.

Similarly to FIG. 2 described above, server 100 establishes a separatecommunications session, separate from the telephone call, for thecommunication of data between MS A and MS B. The separate communicationssession is established on the basis of the received call party details,e.g. TDN A and TDN B, whilst the telephone call is in progress, and iscontinued in parallel with the telephone call, such that voice call datais transmitted via the telephone call and other data can be transmittedvia the communications session, after the establishment of the separatecommunications session.

Communication of data from MS A to MS B can now occur in steps 3 e to 3h by a similar process to that described above for steps 2 d to 2 g inrelation to FIG. 2. Further, communication of data from MS B to MS A cannow occur in steps 3 i to 3 l in a similar process to that describedabove for steps 2 h to 2 k in relation to FIG. 2.

FIG. 4 is a system diagram showing a data communications networkaccording to embodiments. FIG. 4 includes some entities similarlydepicted and labeled to FIG. 1, with such entities functioning in asimilar manner.

The embodiments of FIG. 4, however, involve an analogue telephone(sometimes referred to as a Plain Old Telephone Service (POTS) telephoneor a ‘black phone’), denoted POTS A, located in PSTN A, and a mobilestation MS B located in PLMN B. PSTN A and PLMN B are connected via atelecommunications network 104 comprising one or more PSTNs and/orpacket networks. Further, the user of POTS A also has an associatedpersonal computer PC A connected to packet network 106.

In these embodiments, the user of POTS A cannot conduct communicationssessions separate to voice calls conducted via POTS A just using POTS Aalone. The user of POTS A therefore additionally employs PC A throughwhich separate communications sessions can be conducted. To provide bothvoice calls via POTS A and separate communication sessions via PC A,POTS phone and PC A are coupled together logically.

POTS A has an associated telephone dialing number TDN A and MS B has anassociated telephone dialing number TDN B. PC A has an associatednetwork address in the form of an Internet Protocol (IP) address IP A inpacket network 106. MS B has communications session application softwarerunning on it with an associated identifier AppID B.

PSTN A includes a network element 108 in the form of a call switchingelement, sometimes referred to as a Service Switching Point (SSP), whichis capable of detecting whether a query should be raised in relation tocalls to/from particular telephone dialing numbers by analyzing in-callsignaling information for the calls. Network element 108 acts on behalfof the user of POTS A and PC A and is configured to trigger a query,e.g. hand call control, to a service control point (SCP) network node150 when it detects a predetermined call state for a call to/from TDN Aassociated with POTS A, for example by use of an Intelligent Network(IN) or Advanced Intelligent Network (AIN) call origination/terminationtrigger. SCP 150 is a network node responsible for deciding upon howsuch queries should be dealt with and acting accordingly, for exampleresponding to network element 108 with appropriate instructions. Thequery from network element 108 to SCP 150 may pass via one or moreSignaling Transfer Points (STPs) (not shown).

Upon receipt of in-call signaling information relating to a query fromnetwork element 108, SCP 150 is configured to trigger notification ofsuch to server 100. Any such notification to server 100 will includecall party details for the call, e.g. the TDNs of telephones involved inthe call, TDN A associated with POTS A and TDN B associated with MS B.

Configuration of SCP 150 may involve storing an IP address for server100 in association with TDN A, such that when in-call signalinginformation relating to a call to/from POTS A is received, notificationto server 100 at the stored IP address is triggered.

In the embodiments of FIG. 4, POTS A has no communication sessionapplication software running on it. Further, POTS A has no capability togenerate notifications when a call is outgoing from or incoming to POTSA.

Instead, PC A has communication session application software running onit for facilitating communication sessions according to embodiments.

During installation of the communication session application software onPC A, server 100 is informed that PC A and POTS A are to be coupledtogether logically. PC A sends IP A and TDN A to server 100 whichcreates a record for the user of POTS A and PC A in data store 102containing IP A stored in association with TDN A. Similarly, duringinstallation of the application software on MS B, server 100 is informedof AppID B and creates a record for MS B in data store 102 containingAppID B stored in association with TDN B.

FIG. 5 is a flow diagram depicting operation of embodiments, for exampleimplemented in a system depicted in FIG. 4. Similarly to FIG. 2described above, a voice call is currently in progress between POTS A inPSTN A and MS B in PLMN B, as shown by item 110.

In the case of an outgoing call being made by POTS A to MS B, networkelement 108 receives in-call signaling information for the call,including TDN A, for which an AIN call origination trigger isconfigured. This triggers notification of call party details for thecall to server 100 in step 5 a.

In the case of an incoming call being received by POTS A from MS B,network element 108 receives in-call signaling information for the call,including TDN, for which an AIN call termination trigger is configured.This triggers notification of call party details for the call to server100 in step 5 a.

A call termination/origination trigger relating to a call to/from POTS Awill include call party details for the call, e.g. the TDNs oftelephones involved in the call, TDN A associated with POTS A and TDN Bassociated with MS B.

Application software running on MS B detects the call in progressbetween MS B and POTS A and notifies server 100 of call party detailsfor the call, e.g. the TDNs of telephones involved in the call, TDN Aassociated with POTS A and TDN B associated with MS B, in step 5 b.

In these embodiments, the user of POTS A could be the calling or thecalled party for the call. Call party details are received fromtelephony apparatus acting on behalf of the calling party and telephonyapparatus acting on behalf of the called party, e.g. network element 108and MS B.

Server 100 identifies that the notification of step 5 a from networkelement 108 and the notification of step 5 b from MS B have call partydetails, TDN A and TDN B, in common, e.g. server 100 matches the callparty details received on behalf of each respective party to the call.

Server 100 maps the identity TDN A of POTS A to the network address forPC A, e.g. IP A, by reference to data store 102. Alternatively, IP A maybe received during the call along with the call party details.

Server 100 establishes a communications session, separate from thetelephone call between POTS A and MS B, for the communication of databetween PC A and MS B. The separate communications session isestablished on the basis of the received call party details, e.g. TDN Aand TDN B. Once the separate communications session is established,voice call data is transmitted via the telephone call and other data canbe transmitted via the separate communications session.

Server 100 notifies PC A via IP A that a call has been detected betweenPOTS A and MS B and that a separate communications session has beenestablished between PC A and MS B in step 5 c.

Server 100 updates the records for POTS A/PC A and MS B in data store102 in step 5 d to indicate that a call is in progress between POTS Aand MS B and that a separate communications session between PC A and MSB has been established.

If the user of POTS A and PC A wants to communicate data to MS B, theuser sends the data using PC A to server 100 in step 5 e. Server 100performs a lookup in data store 102 using IP A for PC A in step 5 f andidentifies that a communications session has been established between PCA and MS B separately to the call taking place between POTS A and MS B.Server 100 retrieves TDN B for MS B in step 5 g and transmits the datareceived from PC A to MS B using the retrieved TDN B in step 5 h.

In embodiments, the lookup in data store 102 of step 5 f may also resultin AppID B being retrieved. The data may then be transmitted to MS Busing both TDN B and AppID B, with TDN B being used to locate MS B andAppID B being used to direct the data to the communications sessionapplication software running on MS B.

If the user of MS B wants to send data to the user of POTS A and PC A,the user of MS B sends the data to server 100 in step 5 i. Server 100performs a lookup in data store 102 using TDN A for POTS A in step 5 jand identifies that a communications session has been establishedbetween PC A and MS B separately to the call taking place between MS Band POTS A. Server 100 retrieves IP A for PC A in step 5 k and transmitsthe data received from MS B to PC A using the retrieved IP A in step 5l.

In alternative embodiments, instead of both call party detailnotifications being sent to server 100 in steps 5 a and 5 b, server 100may instead notify MS B of the request from PC A to initiateestablishment of a separate communications session in a similar mannerto step 3 b described above in relation to FIG. 3. Similarly to step 3c, MS B will then transmit a communication session initiation response(in response to user input on MS B indicating acceptance of the request)to server 100 indicating that a communication session separate to thevoice call between POTS A and MS B should be established between MS Band PC A.

Similarly to embodiments described above in relation to FIG. 2, thecommunication session is established in the form of a client-serverrelationship, with server 100 acting as the server and each of PC A andMS B acting as clients. One connection is created between server 100 andPC A and another connection is created between server 100 and MS B. Thetwo connections together create a channel between PC A and MS B throughwhich data can be communicated in either direction.

In some embodiments, establishing the session comprises receiving aclient-server connection request from PC A and establishing aclient-server connection with PC A. In other embodiments, establishingthe session comprises receiving a client-server connection request fromMS B and establishing a client-server connection with MS B.

In embodiments, the client-server connection request is transmitted inresponse to the telephone call between POTS A and MS B beingestablished. In other embodiments, the client-server connection requestis transmitted in response to initiation of a data communicationsservice on PC A after the telephone call between POTS A and MS B isestablished.

If the call between POTS A and MS B is terminated at any stage andserver 100 receives an indication of such, a notification message may betransmitted to PC A to inform it of a change of state of the separatecommunication session.

In alternative embodiments, network element 108 is a call initiatingelement, for example configured to initiate the establishment of thetelephone call between POTS A and MS B in response to a remoteclick-to-dial website action by a user.

FIG. 6 is a flow diagram depicting operation of embodiments, for exampleimplemented in a system depicted in FIG. 4. Network element 108 isconfigured similarly to network element 108 described above in relationto FIG. 4, e.g. when it detects a call to/from TDN A associated withPOTS A, for example by use of an Advanced Intelligent Network (AIN) callorigination/termination trigger, a query to SCP 150 is triggered. Here,however, SCP is configured such that upon receipt of in-call signalinginformation relating to a query from network element 108, notificationto PC A is triggered, instead of notification to server 100. Any suchnotification to PC A will include call party details for the call, e.g.the TDNs of telephones involved in the call, TDN A associated with POTSA and TDN B associated with MS B.

Configuration of SCP 150 may involve storing an IP address IP A for PC Ain association with TDN A, such that when a call is received to/fromPOTS A, PC A can be notified at the stored IP address.

In the embodiments of FIG. 6, when network element 108 detects the callbeing conducted between POTS A and MS B, it transmits call party detailsfor the call, TDN A and TDN B, to PC A in step 6 a. PC A forwards thecall party details notification, including TDN A and TDN B, to server100 in step 6 b.

Application software running on MS B detects the call in progressbetween MS B and POTS A and notifies server 100 of call party detailsfor the call, e.g. the TDNs of telephones involved in the call, TDN Aassociated with POTS A and TDN B associated with MS B, in step 6 c.

In these embodiments, the user of POTS A could be the calling or thecalled party for the call. Call party details are received fromtelephony apparatus acting on behalf of the calling party and telephonyapparatus acting on behalf of the called party, e.g. PC A and MS B.

Steps 6 d to 6 l of FIG. 6 then proceed in a similar manner to steps 5 dto 5 l described above in relation to FIG. 5.

FIG. 7 is a system diagram showing a data communications networkaccording to embodiments. FIG. 7 includes some elements similarlydepicted and labeled to FIG. 4, with such elements functioning in asimilar manner.

In the embodiments of FIG. 7, MS A has communication session applicationsoftware running on it with an associated identifier AppID A. However,MS A does not have application software (or any other capability) fordetecting calls to/from MS A and notifying server 100 of such.

MS B has communication session application software running on it withan associated identifier AppID B. In addition, MS B has applicationsoftware running on it which is capable of detecting calls to/from MS Band notifying server 100 of such.

During installation of the communication session application software onMS A, server 100 is informed of AppID A and creates a record for MS A indata store 102 containing AppID A stored in association with TDN A.Similarly, during installation of the communication session applicationsoftware on MS B, server 100 is informed of AppID B and creates a recordfor MS B in data store 102 containing AppID B stored in association withTDN B.

PLMN A includes a network switching element 108, for example an SSP,capable of generating queries in response to triggers configured forcalls to/from MS A. Network element 108 of FIG. 7 generates queries toSCP 150 in a similar manner to network element 108 described above inrelation to FIG. 4. The network element 108 of FIG. 4 generates queriesin relation to wireline network triggers, for example AdvancedIntelligent Network (AIN) triggers, generated within PSTN of FIG. 4. InFIG. 7, however, the queries are generated in relation to wirelessnetwork triggers such as Customized Applications for Mobile networksEnhanced Logic (CAMEL) or Wireless Intelligent Network (WIN) triggers.

Network switching element 108 is configured to trigger a query includingin-call signaling information to a service control point (SCP) networknode 150 when it detects a call to/from TDN A associated with MS A. Uponreceipt of in-call signaling information relating to a query fromnetwork element 108, SCP 150 is configured to trigger notification ofsuch to server 100. Any such notification to server 100 will includecall party details for the call, e.g. the TDNs of telephones involved inthe call, TDN A associated with POTS A and TDN B associated with MS B.

Configuration of SCP 150 may involve SCP 150 storing an IP address forserver 100 in association with TDN A, such that when in-call signalinginformation relating to a call to/from POTS A is received, notificationto server 100 at the stored IP address is triggered.

FIG. 8 is a flow diagram depicting operation of embodiments, for exampleimplemented in a system depicted in FIG. 7. Similarly to FIG. 2described above, a voice call is currently in progress between MS A inPLMN A and MS B in PLMN B, as shown by item 110.

In the case of an outgoing call being made by MS A to MS B, networkelement 108 receives in-call signaling information for the call,including TDN A, for which a wireless call origination trigger isconfigured. This triggers notification of call party details for thecall to server 100 in step 8 a.

In the case of an incoming call being received by MS A from MS B,network element 108 receives in-call signaling information for the call,including TDN A, for which a wireless call termination trigger isconfigured. This triggers notification of call party details for thecall to server 100 in step 8 a.

A call termination/origination trigger relating to a call to/from MS Awill include call party details for the call, e.g. the TDNs oftelephones involved in the call, TDN A associated with MS A and TDN Bassociated with MS B.

Application software running on MS B detects the call in progressbetween MS B and MS A and notifies server 100 of call party details forthe call, e.g. the TDNs of telephones involved in the call, TDN Aassociated with MS A and TDN B associated with MS B, in step 8 b.

In these embodiments, the user of POTS A could be the calling or thecalled party for the call. Call party details are received fromtelephony apparatus acting on behalf of the calling party and telephonyapparatus acting on behalf of the called party, e.g. network element 108and MS B.

Server 100 identifies that the notification of step 8 a from networkelement 108 and the notification of step 8 b from MS B have call partydetails, TDN A and TDN B, in common and establishes a communicationssession, separate from the telephone call between MS A and MS B, for thecommunication of data between MS A and MS B. The separate communicationssession is established on the basis of the received call party details,e.g. TDN A and TDN B. Once the separate communications session isestablished, voice call data is transmitted via the telephone call andother data can be transmitted via the separate communications session.

Server 100 notifies MS A that a call has been detected between MS A andMS B and that a separate communications session has been establishedbetween MS A and MS B in step 8 c.

Server 100 updates the records for MS A and MS B in data store 102 instep 8 d to indicate that a call is in progress between MS A and MS Band that a separate communications session between MS A and MS B hasbeen established.

Communication of data from MS A to MS B can now occur in steps 8 e to 8h by a similar process to that described above for steps 2 d to 2 g inrelation to FIG. 2. Further, communication of data from MS B to MS A cannow occur in steps 8 i to 8 l in a similar process to that describedabove for steps 2 h to 2 k in relation to FIG. 2.

In alternative embodiments, instead of both call party detailnotifications being sent to server 100 in steps 8 a and 8 b, server 100may instead notify MS B of the request from MS A to initiateestablishment of a separate communications session in a similar mannerto step 3 b described above in relation to FIG. 3. Similarly to step 3c, MS B will then transmit a communication session initiation response(in response to user input on MS B indicating acceptance of the request)to server 100 indicating that a communication session separate to thevoice call between MS A and MS B should be established between MS B andMS A.

FIG. 9 is a system diagram showing a data communications networkaccording to embodiments. FIG. 9 includes some entities similarlydepicted and labeled to FIG. 4, with such entities functioning in asimilar manner. In addition, the system of FIG. 9 includes a contentserver 120 connected to packet network 106 at which electronic contentcan be provided, for example via electronic download. The electroniccontent could comprise software components such as applications orplug-ins, or media data such as music, videos, computer games, etc.

FIG. 10 is a flow diagram depicting operation of embodiments, forexample implemented in a system depicted in FIG. 9. Similarly to FIG. 5described above, a voice call is currently in progress between POTS A inPSTN A and MS B in PLMN B, as shown by item 110.

Similarly to steps 5 a to 5 d described above in relation to FIG. 5,steps 10 a to 10 d of FIG. 10 depict detection of a voice call betweenPOTS A and MS B by network element 108 and notification of such toserver 100, detection of the call between POTS A and MS B by MS B andnotification of such to server 100, establishment of a separatecommunications session between PC A and MS B and notification of such toPC A, and updating of data store 102.

In these embodiments, the user of POTS A and PC A wishes to use asoftware component in the separate communications session with MS B andtransmits from PC A an identifier for the software component, forexample an application name, file name or Uniform Resource Locator(URL), to server 100 in step 10 e. The software component may forexample comprise a plug-in relating to the communications sessionapplication software installed on MS B and PC A.

Server 100 performs a lookup in data store 102 using IP A for PC A instep 10 f and identifies that a communications session, separate to thevoice call between POTS A and MS B, has been established between PC Aand MS B. Server 100 retrieves TDN B for MS B in step 10 g and proceedsto enable download of the software component by MS B.

Server 100 enables the download by transmitting the identifier for thesoftware component received from PC A to MS B in step 10 h. Theidentifier could be transmitted to MS B embedded in a text message suchas an SMS message.

Using the received software component identifier, MS B sends a downloadrequest for the software component to content server 120 in step 10 i.Content server then provides the software component to MS B in step 10j.

If the user of MS B wants to communicate data relating to use of thesoftware component to the user of POTS A and PC A, MS B transmits suchdata to server 100 in step 10 k. When server 100 receives the data fromMS B in step 10 k it performs a lookup in data store 102 using TDN B forMS B in step 10 l and identifies that a separate communications sessionhas been established between PC A and MS B. Server 100 retrieves IP Afor PC A in step 10 n and transmits the data received from MS B to PC Ain step 10 o. Data may be communicated from PC A to MS B in a similarmanner as per steps 2 h to 2 k described above in relation to FIG. 2.

When server 100 receives the software component identifier in step 10 e,it may identify that further information is required for downloading thesoftware component, for example if only an application name is suppliedby PC A. The further information could include an IP address, domainname or URL for locating content server 120 in packet network 106; suchfurther information may be stored locally to server 100 or could beobtained via a search or query process carried out by server 100 withinpacket network 106 or beyond. In such a case, server 100 willadditionally provide such further information to MS B in step 10 h.

In alternative embodiments, when server 100 receives the softwarecomponent identifier in step 10 e, it performs a lookup in data store102 and identifies that that a separate communications session has beenestablished between PC A and MS B. Server 100 then downloads thesoftware component from content server 120 itself using the softwarecomponent identifier received from PC A, and transmits the softwarecomponent directly to MS B.

In further alternative embodiments, instead of PC A transmitting anidentifier for the software component to server 100 as per step 10 e, PCA transmits the software component itself to server 100. Server 100performs a lookup in data store 102 and identifies that that a separatecommunications session has been established between PC A and MS B andtransmits the software component received from PC A to MS B.

In embodiments, before download of the software component to MS B or PCA is enabled, a capability check is conducted to determine whether MS Bor PC A is initially enabled with the software component. If thecapability check indicates that the respective user device is notinitially enabled with the software component, then enabling of thedownload may proceed.

In some embodiments, capability data for one or more user devices isstored in data store 102 and server 100 may carry out a capability checkby reference to data store 102. In other embodiments, the capabilitycheck involves transmitting a capability query to a user device, andreceiving a response indicating whether said the device is initiallyenabled with the software component.

In embodiments, the separate communications session is established usinga session establishment software application or operating systemfunction on the user device to which the software component is beingdownloaded to and the software component is a software application whichinteroperates with the session establishment software application oroperating system function.

In embodiments, a client-server connection request is transmitted by theuser device to which the software component is being downloaded toserver 100 and a client-server connection is established between server100 and that device. The software component is transmitted via theestablished client-server connection. The client-server connectionrequest could be transmitted in response to the telephone call beingestablished or in response to a notification received during thetelephone call, after the telephone call is established.

FIG. 11 is a flow diagram depicting operation of embodiments, forexample implemented in a system depicted in FIG. 9. Similarly to FIG. 10described above, a voice call is currently in progress between POTS A inPSTN A and MS B in PLMN B, as shown by item 110.

Steps 11 a to 11 c of FIG. 11 depict detection of a voice call betweenPOTS A and MS B by network element 108 and notification of call partydetails for such to server 100, detection of the call between POTS A andMS B by MS B and notification of call party details for such to server100, as well as notification of the detected call to PC A.

When server 100 receives the call party details for the call betweenPOTS A and MS B in steps 11 a and 11 b, it performs a lookup in datastore 102 for the TDNs of MS A and MS B in step 11 d. From the lookupinformation received in step 11 e, server 100 identifies that MS B is aninitially non-enabled user device that does not currently have acapability associated with participating in a communication sessionseparate to the voice call between POTS A and MS B.

For example, a data record for MS B in data store 102 may indicate thatMS B does not have communications session software installed on it, orthere may be no data record at all for MS B in data store 102 which alsoindicates that MS B does not have communications session softwareinstalled on it.

In these embodiments, in order to provide the initially non-enabled userdevice MS B with the capability associated with participating in thesession, server 100 enables the download of a software application tothe initially non-enabled user device MS B.

Server 100 enables the download of the software application bytransmitting an identifier for the software application to MS B in step11 f. The identifier could be transmitted to MS B embedded in a textmessage such as an SMS message.

Using the received software application identifier, MS B sends adownload request for the software application to content server 120 instep 11 g. Content server then provides the software application to MS Bin step 11 h.

MS B proceeds to install the software application, which when installed,sends an installation confirmation message to server 100 in step 11 i.Server 100 is now able to establish a communications session between PCA and MS B which is separate to the voice call being conducted betweenPOTS A and MS B.

Once the separate communications session between MS B and PC A isestablished, MS B may communicate data to PC A as shown in steps 11 j to11 m in a similar manner to steps 5 i to 5 l as described above inrelation to FIG. 5. Further, communication of data from MS B to MS A cannow occur (not shown) in a similar process to that described above forsteps 5 e to 5 h in relation to FIG. 5.

In embodiments, establishment of the separate communications session maybe initiated by the user of POTS A and PC A, for example by user inputon PC A. The user input causes communications session software installedon PC A to transmit a communications session initiation request messageto server 100 which then proceeds to establish a separate communicationssession as described above.

FIG. 12 is a system diagram showing a data communications networkaccording to embodiments. FIG. 12 includes some entities similarlydepicted and labeled to FIG. 4, with such entities functioning in asimilar manner. In addition, the system of FIG. 12 includes anauthorization server 122 connected to packet network 106 at whichauthorization for use of copyrighted electronic content can be requestedand granted. The electronic content could comprise software componentssuch as applications and plug-ins, or media data such as music, videos,etc.

FIG. 13 is a flow diagram depicting operation of embodiments, forexample implemented in a system depicted in FIG. 12. Similarly to FIG. 5described above, a voice call is currently in progress between POTS A inPSTN A and MS B in PLMN B, as shown by item 110.

Similarly to steps 5 a to 5 d described above in relation to FIG. 5,steps 13 a to 13 d of FIG. 13 depict detection of a voice call betweenPOTS A and MS B by network element 108 and notification of call partydetails for such to server 100, detection of the call between POTS A andMS B by MS B and notification of such to server 100, establishment of aseparate communications session between PC A and MS B and notificationof such to PC A, and updating of data store 102 accordingly.

In these embodiments, the user of POTS A and PC A, transmits from PC Aan identifier identifying a feature of the communications sessionseparate to the voice call between POTS A and MS B that requiresauthorization for use by MS B in step 13 e. The feature could forexample be a software component or media data and the identifier couldbe a URL or other network address at which the feature can be located.

Upon receipt of the feature identifier, server 100 transmits anauthorization requirement query containing the feature identifier toauthorization server 122 in step 13 f. The authorization requirementquery has the effect of asking the authorization server whetherauthorization for use of the identified feature by MS B in the separatecommunications session is required. Authorization server 122 performsany appropriate checks, for example with reference to a copyrightrecords database (not shown), and transmits an authorization requirementresponse back to server 100 in step 13 g. In this case, theauthorization requirement response of step 13 g indicates thatauthorization for use of the identified feature by MS B is required, forexample “A copyright fee of $xx must be paid” for use of the identifiedfeature in the separate communications session.

Server 100 now requests authorization from the user of PC A and POTS Ato authorize the use of the identified feature by MS B in the separatecommunications session in step 13 h, for example asking the user of POTSA and PC A whether they are willing to accept the $xx copyright charge.The user of POTS A and PC A accepts the charge by appropriate input viaPC A which results in an indication of authorization being transmittedfrom PC A to server 100 in step 13 i.

When server 100 receives the authorization indication of step 13 i fromPC A, server 100 enables the use of the feature by MS B in the separatecommunications session. Server 100 contacts authorization server 122 instep 13 j requesting that authorization for the identified feature begranted. Server 122 responds to server 100 with an authorization grantin step 13 k.

Granting authorization may involve authorization server contacting apayment server of an appropriate financial institution on behalf of theuser device in question, for example to pay a copyright fee for use ofthe feature. The charge will generally be passed on to a an accountassociated with the user of POTS A and PC A because it is that user whois requesting use of the identified feature by the user of MS B in theseparate communications session.

The user of PC A is informed that authorization of the feature has beengranted by a message transmitted from server 100 to PC A in step 13 l,for example including confirmation of the amount charged to theiraccount.

Server 100 enables use of the feature for MS B by transmitting anidentifier for the feature along with an authorization token provingthat use of the feature by MS B has been authorized. The user of MS Bcan then download (not shown) or otherwise access the feature using thefeature identifier and authorization token received from server 100without having to request authorization (or pay for such). Download ofthe feature may involve contacting a content server such as item 120 inFIG. 9.

The authorization token may include a purchase token proving that acopyright fee or suchlike has already been paid for use of the feature.

In some embodiments, the feature may involve using a service applicationwhich requires authorization in order to process service datatransmitted during the separate communications session. In alternativeembodiments, the feature may involve accessing data which requiresauthorization in relation to which an identifier is transmitted duringthe separate communications session.

FIG. 14 is a flow diagram depicting operation of embodiments, forexample implemented in a system depicted in FIG. 7. Similarly to FIG. 2described above, a voice call is currently in progress between MS A inPLMN A and MS B in PLMN B, as shown by item 110. MS B and MS A includegeographical location modules, such as Global Positioning System (GPS)modules, capable of receiving geographical location data based on thephysical location of MS A and MS B respectively. MS A and MS B both havemap creation applications for creating maps for display on MS A and MS Brespectively.

FIG. 14 depicts embodiments where the geographical location of MS B is‘pulled’ from MS B by MS A.

Network element 108 receives in-call signaling information for the callbetween MS A and MS B which triggers notification of call party details,including TDN A and TDN B, for the call to server 100 in step 14 a.

Application software running on MS B detects the call in progressbetween MS B and MS A and notifies server 100 of call party details forthe call, e.g. the TDNs of telephones involved in the call, TDN Aassociated with MS A and TDN B associated with MS B, in step 14 b.

Server 100 identifies that the notification of step 14 a from networkelement 108 and the notification of step 14 b from MS B have call partydetails, TDN A and TDN B, in common and establishes a communicationssession, separate from the telephone call between MS A and MS B, for thecommunication of data between MS A and MS B. The separate communicationssession is established whilst the telephone call is in progress on thebasis of the received call party details, e.g. TDN A and TDN B. Once theseparate communications session is established, voice call data istransmitted via the telephone call and other data can be transmitted viathe separate communications session.

Server 100 notifies MS A that a call has been detected between MS A andMS B and that a separate communications session has been establishedbetween MS A and MS B in step 14 c.

Server 100 updates the records for MS A and MS B in data store 102 instep 14 d to indicate that a call is in progress between MS A and MS Band that a separate communications session between MS A and MS B hasbeen established.

In these embodiments, the user of MS A wishes to obtain geographicallocation data for MS B, for example to use in relation to a map creationapplication running on MS A. MS A transmits a geographical locationcapability check message to server 100 in step 14 e; the capabilitycheck message is for checking the capability of MS B to providegeographical location data relating to its physical location, forexample checking if MS B has a map creation application running on it.

Server 100 forwards the geographical location capability check messageon to MS B in step 14 f. Mobile station MS B responds by sending ageographical location capability response message to server 100 in step14 g which forwards this on to MS A in step 14 h; the capabilityresponse message includes information as to whether MS B can providegeographical location data relating to its physical location.

In this embodiment, the capability response message informs MS A that MSB is able to provide geographical location data (by use of itsgeographical location module), so MS A transmits a request forgeographical location data for MS B to server 100 in step 14 i. Server100 forwards the request from MS A to MS B in step 14 j.

When MS B receives the request for geographical location data fromserver 100 in step 14 j, MS B instructs its geographical location moduleto carry out a geographical location process and provide geographicallocation data relating to the physical location of MS B in step 14 k.The geographical location data resulting from step 14 k is transmittedto server 100 in step 14 l. Server 100 then transmits data including orderived from the geographical location data received in step 14 l to MSA in step 14 m.

The map creation application of MS A can use the geographical locationdata received from server 100 in step 14 m to create a map whichincorporates a representation of the physical location of MS B. Forexample, the received geographical location data may include a gridreference or longitude and latitude parameters which can be processed bythe map creation application to plot the location of MS B within a mapstored or accessible by MS A. Such embodiments could for example beuseful for the user of MS A to give directions to MS B verbally duringthe telephone call being conducted via MS A and MS B with reference tothe created map and indication of the location of MS B thereon.

In embodiments, steps 14 i to 14 m are repeated, allowing display of adynamically updating map on MS A that shows changes in the physicallocation of MS B as they happen. Alternatively, steps 14 k to 14 m canbe repeated allowing updating of the map on MS A without furtherrequests as per steps 14 i and 14 j being required.

In embodiments where MS B is not able to provide geographical locationdata, for example because MS B has no geographical location module orother such capability, the capability response message of step 14 g willstate so, thus informing MS A that communication of geographicallocation data from MS B is not possible. In alternative embodimentswhere MS B is not able to provide geographical location data, MS B maynot send any capability response message, and after a predeterminedperiod with no response being received, MS A might conclude thatcommunication of geographical location data from MS B will not bepossible.

In further alternative embodiments, the geographical location capabilitycheck message of step 14 e can be combined with the request forgeographical location data of step 14 i and the geographical locationcapability response message of step 14 g can be combined with thetransmittal of geographical location data of step 14 l.

FIG. 15 is a flow diagram depicting operation of embodiments, forexample implemented in a system depicted in FIG. 7. In FIG. 15, steps 15a to 15 d occur in a similar manner as per steps 14 a to 14 d describedabove in relation to FIG. 14.

FIG. 15 depicts embodiments where the geographical location of MS A is‘pushed’ from MS A to MS B.

In these embodiments, the user of MS A wishes to send geographicallocation data for MS A to MS B.

Embodiments involve MS A checking the capability of MS B to processand/or display geographical location data by transmitting a geographicallocation capability check message to server 100 in step 15 e. Server 100forwards the geographical location capability check message on to MS Bin step 15 f. Mobile station MS B responds by sending a geographicallocation capability response message to server 100 in step 15 g whichforwards this on to MS A in step 15 h.

In this embodiment, the capability response message informs MS A that MSB is able to process geographical location data (by use of its mapcreation application), so the user of MS A triggers generation ofappropriate geographical location data by appropriate input to themapping application of MS A. Alternatively, generation of geographicallocation data could occur upon receipt of the capability responsemessage of step 15 h without any input from the user of MS A beingrequired.

MS A instructs its geographical location module to carry out ageographical location process and provide geographical location datarelating to the physical location of MS A in step 15 i. The geographicallocation data resulting from step 15 i is transmitted to server 100 instep 15 j. Server 100 then transmits data including or derived from thegeographical location data received in step 15 j to MS B in step 15 k.

The map creation application of MS B can use the geographical locationdata received from server 100 in step 15 k to create a map whichincorporates a representation of the physical location of MS A. Suchembodiments could for example be useful for the user of MS B to givedirections to the user of MS A verbally during the telephone call beingconducted via MS A and MS B with reference to the created map andindication of the location of MS A thereon.

In embodiments, steps 15 i to 15 k can be repeated, allowing display ofa dynamically updating map on MS B that depicts changes in the physicallocation of MS A as they occur.

In alternative embodiments, MS B has no map creation application forcreating maps for display on MS B, but does have the capability todisplay images, such information being indicated in the locationcapability response message of step 15 g. In such embodiments, the MS Aitself plots a map containing a physical representation of its physicallocation and creates an map image (for example a screenshot from the mapcreation application) depicting this information for transmittal to MS Bvia server 100 in steps 15 j and 15 k; these steps would thereforeinvolve transmittal of media (image) data. Upon receipt of the imagedata, MS B is able to display the image of the map created and providedby MS A, thus allowing the user of MS B to view a representation of thephysical location of MS A even though MS B has no map creationcapability itself.

In further alternative embodiments where MS B has no map creationapplication for creating maps for display on MS B, but does have thecapability to display images, a network link, such as a URL, for anonline mapping service such as Google Maps™ is transmitted to MS B. Thenetwork link contains information relating to the physical location ofMS A and can be created by MS A and transmitted to server 100 fortransmittal on to MS B, or can be derived from the geographical locationdata received from MS A by server 100 and transmitted on to MS B. WhenMS B receives the network link, it accesses the mapping service usingthe received network link. The mapping service uses the information inthe network link relating to the physical location of MS A to generate amap image including a representation of the physical location of MS Aand transmits the map image to MS B. Once MS B has downloaded the mapimage, it displays the map image to the user of MS B, thus allowing theuser of MS B to view a representation of the physical location of MS Aeven though MS B has no map creation capability itself.

In embodiments, the geographical location data is received by server 100in the form of a data object including geographical coordinate data. Acapability check can then be carried out by server 100 in relation towhether the respective user device is capable of processing thegeographical coordinate data during the separate communications session.If the capability check indicates that the respective user device iscapable of processing the geographical coordinate data, server 100 willtransmit the geographical coordinate data during the separatecommunications session.

Establishing the separate communication session may comprise receiving aclient-server connection request from, and establishing a client-serverconnection with the appropriate user device, and transmitting the dataincluding or derived from the received geographical location data viathe client-server connection.

Embodiments described below in relation to FIGS. 16 to 21 involveestablishing a communications session for communication of data betweenat least two devices in a data communications network. In theseembodiments, one of the at least two devices comprises a telephony userdevice comprising a reconfigurable graphical user interface. Another ofthe at least two devices comprises a device associated with a serviceprovider. The service provider also has one or more associated telephonydevices.

FIG. 16 is a system diagram according to embodiments. Similarly, to FIG.1, FIG. 16 includes mobile station MS A, PLMN A, telecommunicationsnetwork 104, packet network 106, server 100 and data store 102. FIG. 16also includes a PSTN B which functions in a similar manner to PSTN A asdescribed above in relation to FIG. 4.

FIG. 16 also includes a service provider system 400 comprising anautomatic call distributing system 404 (denoted ‘ACD’), a datacommunications part 406, a service provider data store 402 and a servicemanagement part. Service provider system 400 also includes a number ofuser agent positions UA 1, UA 2, UA 3, with each user agent positioncomprising a user agent telephony device and a user agent computingdevice. Each user agent telephony device is connected to ACD 404. Eachuser agent computing device is connected to data communications part 406via a Local Area network (LAN) or suchlike.

ACD 404 is capable of distributing incoming telephone calls to one ormore user agents at which respective user agent operators are available.Incoming calls to the service provider system are distributed accordingto the availability of user agent operators at their associated useragent positions. When an incoming call from a customer is distributed toan available user agent position, a user agent operator associated withthat user agent position can speak to the customer via their associateduser agent telephony device and can process service data related to aservice being provided to the customer via their associated computingdevice.

Data communications part 406 comprises a computing device such as aserver with Computer Telephony Integration (CTI) capabilities. Datacommunications part 406 uses CTI techniques to provide user agentoperators with information displayed via their associated user agentcomputing devices relating to calls they are conducting with customers.Data communications part 406 is capable of establishing and/orprocessing communication sessions between user agent computing devicesand devices external to service provider system 400. Incoming data whichdata communications part 406 receives from an external device via acommunication session can be passed on to the appropriate user agentcomputing device and vice versa for outgoing data from a user agentcomputing device.

FIG. 17 is a flow diagram depicting operation of embodiments using thesystem of FIG. 16.

Telephony user device MS A is capable of establishing a communicationssession for communication of data with respect to at least one otherdevice in a data communications network. MS A includes a reconfigurablegraphical user interface.

The user of MS A dials the telephone dialing number associated withservice provider system 400 which results in automatic call distributingsystem 404 receiving the incoming call. ACD 404 proceeds to identify anavailable user agent operator to take the incoming call. In theseembodiments, the user of MS A is a customer of the service provider.

ACD 404 identifies that a user agent operator is available at a useragent position (for example agent position ‘UA 1’ depicted in FIG. 16)having an associated telephone (depicted ‘UA Telephone’ in FIG. 17) andcomputing device, and distributes the call to that UA Telephoneaccordingly. A voice call is thus established between MS A and UATelephone, as shown by item 110.

Application software running on MS A detects that there is a call inprogress between MS A and UA Telephone and notifies server 100 of callparty details for the call, in step 17 a. The call party details of step17 a may comprise a TDN associated with MS A and a TDN associated withservice provider system 400.

ACD 404 notifies data communications part 406 that a call is in progressbetween UA Telephone and MS A. Data communications part 406 notifiesserver 100 of call party details for the call, in step 17 b. The callparty details of step 17 b may comprise a TDN associated with MS A and aTDN associated with service provider system 400. The call party detailsof step 17 b may also comprise an extension number associated with UATelephone.

Server 100 establishes a separate communications session, separate fromthe telephone call between MS A and UA Telephone, for the transfer ofdata between MS A and data communications part 406, as shown by item111. The session is established on the basis of the one or more callparty details associated with the telephone call. Data communicationspart 406 forwards data received via the separate communication sessionto the computing device associated with the user agent operator of UAtelephone and vice versa as and when necessary.

Upon establishment of the separate communications session, server 100sends a request for configuration data determined by the serviceprovider to data store 102 in step 17 c, resulting in configuration datadetermined by the service provider being retrieved in step 17 d. Server100 transmits the retrieved configuration data to MS A via the separatecommunication session in step 17 e.

When MS A receives the configuration data of step 17 e, it reconfiguresat least a first part of its graphical user interface according to thereceived configuration data, as shown by step 17 f.

MS A confirms to server 100 that it has reconfigured at least a firstpart of its graphical user interface according to the receivedconfiguration data in step 17 g and server 100 in turn notifies datacommunications part 406 of such in step 17 h. Data communications part406 notifies the appropriate user agent computing device of thereconfiguration such that the user agent operator conducting thetelephone call with the user of MS A knows that the graphical userinterface of MS A has been reconfigured according to the configurationdata. The user agent operator can thus conduct the call accordingly, forexample referring to information displayed via the reconfiguredgraphical user interface during the call.

In the above embodiments, the configuration data has been predeterminedby the service provider prior to the call and provided to server 100 forstorage in data store 102. Server 100 is thus able to retrieve thepredetermined configuration data from data store 102 upon establishmentof the separate communications session without having to contact serviceprovider system 400.

FIG. 18 is a flow diagram depicting operation of embodiments using thesystem of FIG. 16.

In these embodiments, the configuration data has been predetermined bythe service provider prior to the call, but has not been provided toserver 100. Instead, the predetermined configuration is stored inservice provider data store 402.

Similarly to the embodiments of FIG. 17, a call is currently in progressbetween MS A and UA Telephone, as shown by item 110, MS A notifiesserver 100 of the call in progress in step 18 a, data communicationspart 406 notifies server 100 of the call in progress in step 18 b, and aseparate communication session is established between MS A and datacommunications part 406 as shown by item 111.

In these embodiments, upon establishment of the separate communicationssession, server 100 sends a request for configuration data determined bythe service provider (for transmittal to MS A) to data communicationspart 406 in step 18 c. Data communications part 406 forwards theconfiguration data request to service provider data store 402 in step 18d. This results in configuration data determined by the service providerbeing retrieved by data communications part 406 in step 18 e whichforwards the retrieved configuration data to server 100 in step 18 f.

Server 100 transmits the retrieved configuration data to MS A via theseparate communication session in step 18 g. When MS A receives theconfiguration data of step 18 g, it reconfigures at least a first partof its graphical user interface according to the received configurationdata, as shown by step 18 h. MS A confirms to server 100 that it hasreconfigured the at least first part of its graphical user interfaceaccording to the received configuration data in step 18 i and server 100in turn notifies data communications part 406 of such in step 18 j.

FIG. 19 is a flow diagram depicting operation of embodiments using thesystem of FIG. 16. These embodiments depict processes carried out eitherafter those described above in relation to FIG. 17 or after thosedescribed above in relation to FIG. 18.

Item 112 of FIG. 19 indicates one or more steps involving interactionbetween MS A, server 100 and/or service provider computing device 406during the call between the user of MS A and the user agent operatorassociated with UA Telephone. Some examples of such interaction aredescribed later below.

During the call, the user agent operator associated with serviceprovider computing device 406 realizes that further reconfiguration ofthe graphical user interface of MS A during the call, i.e. dynamicreconfiguration, is desirable and proceeds to initiate dynamicreconfiguration accordingly. This involves the user agent operatorproviding user input to their agent position computing device, forexample selecting an appropriate action from an on-screen menu on adisplay part of the agent position computing device.

The user input is passed to data communications part 406 which sends arequest for appropriate dynamic configuration data to service providerdata store 402 accordingly in step 19 a. The configuration data isdynamic because it is related to a reconfiguration process occurringduring the call.

Dynamic configuration data is retrieved by data communications part 406in step 19 b which transmits the retrieved dynamic configuration data onto server 100 via the separate communication session in step 19 c.

Server 100 transmits the dynamic configuration data received in step 19c to MS A via the separate communication session in step 19 d. When MS Areceives the dynamic configuration data of step 19 d, it reconfigures atleast a second part of its graphical user interface according to thereceived dynamic configuration data, as shown by step 19 e. MS Aconfirms to server 100 that it has reconfigured the at least second partof its graphical user interface according to the received configurationdata in step 19 f and server 100 in turn notifies data communicationspart 406 of such in step 19 g.

The user agent operator conducting the telephone call with the user ofMS A now knows that the graphical user interface of MS A has beenreconfigured according to the dynamic configuration data. The user agentoperator can thus conduct the call accordingly, for example referring toinformation displayed via the dynamically reconfigured graphical userinterface during the call.

FIG. 20 shows a front view of a mobile telephony device MS A accordingto embodiments. In FIG. 20, MS A comprises an exemplary mobile telephonydevice, although embodiments may equally be applied to a non-mobilecomputing device and/or other computing device with telephonycapabilities. MS A can comprise a variety of different hand-helddevices, for example a smartphone, Personal Digital Assistant (PDA) orPersonal Pocket Computer (PCC). MS A comprises memory storage and one ormore processors (not shown) for data processing purposes includingimplementation of an operating system, for example an Android™,Symbian™, Blackberry™ or Windows Phone™ operating system. The operatingsystem provides a platform for execution of application software (or‘applications’ or ‘apps’) for allowing a user to perform different taskson MS A. The application software may be installed during manufacture ormay be downloaded and installed by a user of MS A.

MS A comprises a body 502, hard-wired input keys 508, 510, 512, 514 anda power on/off button 506. MS A comprises a touch-screen user interface504 which is operable to output a graphics display and receive input viauser touches on the interface. Hard-wired input keys 508, 510, 512, 514may be operable to execute common operations such as ‘Open menu’, ‘Go tohome screen’, ‘Go back to last screen’, etc. Alternatively, one or morehard-wired input keys 508, 510, 512, 514 may be implemented as soft keyson touch-screen 504.

MS A supports a variety of different communication methods includingtelephony functionality enabling a user to conduct incoming and outgoingtelephone calls with one or more remote users in a telecommunicationsnetwork (not shown). MS A comprises a number of components (not shown)which are known in the art, the operation of which is not described herein detail, including one or more radio frequency transceiver(s) andaerial(s), a speech coder/decoder connected to a loudspeaker and amicrophone, and, in some embodiments, a removable Subscriber IdentityModule (SIM) connected via electrical contacts.

MS A includes data transfer capabilities, including data packetinput/output via a data input-output interface with one or more InternetProtocol (IP) parts of the telecommunications network. MS A may includemessaging functionality, for example Short Message Service (SMS) andMultimedia Messaging Service (MMS) messaging.

In these embodiments, the user of MS A is currently conducting a callwith a user agent operator of service provider system 400 as describedabove in relation to FIGS. 16 to 19. An in-call screen application isthus configured to display an in-call screen on touch-screen userinterface 504. The in-call screen displayed on touch-screen userinterface 504 includes a number of soft-keys which are responsive touser touches to provide input to the in-call screen application runningon mobile telephony device MS A. The soft-keys include dial-pad digits1, 2, . . . to 0 and the * (‘star’) and # (‘hash’) symbols which areused for entering telephone dialing numbers. The soft-keys also includeseveral other soft-keys 516, 518, 520, 522, 524, 526 which are operableto initiate other in-call functionality in response to user input, forexample end-call, call-hold, mute, speaker-phone, and show/hide dial-padoperations.

FIG. 21 shows a front view of MS A according to embodiments. In theseembodiments, the user of MS A is currently conducting a call with a useragent operator of service provider system 400 as described above inrelation to item 110 of FIG. 17 or 18. Similarly, a separatecommunications session has been established between MS A and serviceprovider data communications part 406 as per item 111 of FIG. 17 or 18.

In these embodiments, configuration data determined by the serviceprovider prior to the call has been received by MS A via the separatecommunication session, as per steps 17 c to 17 e of FIG. 17 or steps 18c to 18 g of FIG. 18. MS A reconfigures at least a first part of itstouch-screen user interface 504 according to the received predeterminedconfiguration data, as depicted by step 17 f of FIG. 17 or step 18 h ofFIG. 18.

In these embodiments, the reconfiguration results in an overlay portionbeing displayed over the at least first part of the screen as shown byitem 530 in FIG. 21. In these embodiments, overlay portion 530 comprisesa translucent layer such that the portion of the screen below overlayportion 530 is visible through overlay portion 530. In this case, thesoft-keys for digits ‘5’ and ‘6’ on the dial-pad part of the in-callscreen can be seen through translucent overlay portion 530.

In these embodiments, overlay portion 530 comprises severaltouch-sensitive screen regions 550, 552, 554 which are operable toinitiate one or more operations of MS A independently of the in-callscreen application in response to user input via touch-sensitive screenregions 550, 552, 554. This means that user input via any oftouch-sensitive screen regions 550, 552, 554 will be passed to otherapplication software of MS A rather than to the in-call screenapplication displaying the in-call screen below the overlay portion,e.g. pressing touch-sensitive screen region 550 will not provide a userinput of the dial-pad digits ‘5’ or ‘6’ to the in-call screenapplication, but rather will be passed to other application software ofMS A for processing.

Embodiments therefore allow other tasks to be initiated on MS A which donot involve sending data associated with user input, such as in-bandDual-Tone Multi-Frequency (DTMF) tones, via the telephone call beingconducted between MS A and the UA Telephone.

Embodiments therefore allow other tasks to be initiated on MS A which donot involve sending data associated with user input via thecommunication session established between MS A and data communicationspart 406.

FIG. 22 shows a front view of MS A according to embodiments. In theseembodiments, the user of MS A is currently conducting the same call withthe user agent operator of service provider system 400 as describedabove in relation to FIG. 21. Similarly, the separate communicationssession established between MS A and service provider datacommunications part 406 is in place.

In these embodiments, dynamic configuration data has been received by MSA via the separate communication session, as per steps 19 a to 19 d ofFIG. 19. MS A reconfigures at least a second part of its touch-screenuser interface 504 according to the received dynamic configuration data,as depicted by step 17 f of FIG. 17 or step 18 h of FIG. 18.

In these embodiments, the reconfiguration results in a further overlayportion being displayed over the at least second part of the screen asshown by item 570 in FIG. 22. In these embodiments, overlay portion 570comprises a translucent layer such that the portion of the screen belowoverlay portion 570 is visible through overlay portion 570. In thiscase, the soft-keys for digits ‘8’ and ‘9’ on the dial-pad part of thein-call screen can be seen through translucent overlay portion 570.

In these embodiments, overlay portion 570 comprises a furthertouch-sensitive screen region 572 which is operable to initiate one ormore operations of MS A independently of the in-call screen applicationin response to user input via touch-sensitive screen region 572. Thismeans that user input via touch-sensitive screen region 572 will bepassed to other application software of MS A rather than to the in-callscreen application displaying the in-call screen below the overlayportion, e.g. pressing touch-sensitive screen region 572 will notprovide a user input of the dial-pad digit ‘9’ to the in-call screenapplication, but rather will be passed to other application software ofMS A for processing.

Embodiments therefore allow other tasks to be initiated on MS A which donot involve sending data associated with user input via the telephonecall being conducted between MS A and the UA Telephone.

Embodiments therefore allow other tasks to be initiated on MS A which donot involve sending data associated with user input via thecommunication session established between MS A and data communicationspart 406.

In embodiments, touch-screen user interface 504 will be reconfigured todisplay touch-sensitive screen regions 550, 552, 554 upon establishmentof the separate communication session. However, touch-screen userinterface 504 may not be reconfigured to display touch-sensitive screenregion 572 until some time later during the call between the user of MSA and the user agent operator of service provider system 400.

To help draw the attention of the user of MS A to the fact thatreconfiguration of touch-screen user interface 504 to displaytouch-sensitive screen region 572 has occurred, the at least first part530 of touch-screen user interface 504 can display touch-sensitivescreen regions 550, 552, 554 in a first display mode and the at leastsecond part 570 of touch-screen user interface can displaytouch-sensitive screen region 572 in a second display mode. Thedifferent display modes allow a user of MS A to more easily distinguishbetween the different touch-sensitive screen regions.

The second display mode could involve displaying touch-sensitive screenregion 572 as a flashing icon, whereas the first display mode couldinvolve displaying touch-sensitive screen regions 550, 552, 554 asnon-flashing icons. Alternatively, the second display mode could involvedisplaying touch-sensitive screen region 572 as a wobbling icon, whereasthe first display mode could involve displaying touch-sensitive screenregions 550, 552, 554 as still icons.

In the embodiments described above in relation to FIGS. 20 to 22,predetermined configuration data is transmitted to MS A in order toreconfigure at least a first part of its touch-screen user interface.The reconfiguration results in one or more touch-sensitive screenregions being added to the screen in the form of a number of icons or‘buttons’. The user of MS A can touch the on-screen icons in order toinitiate a variety of tasks, for example tasks associated with theservice being provided by the service provider. The icons thus functionas items of a menu from which the user of MS A can select actions oftheir choosing.

These embodiments also involve dynamic configuration data beinggenerated and transmitted to MS A in order to reconfigure at least asecond part of its touch-screen user interface such that one or moreadditional touch-sensitive screen regions are added to the screen in theform of a number of additional icons or ‘buttons’. The additional iconsthus function as additional items in the menu. Embodiments thereforeprovide processes by which the list of menu items can be expanded orotherwise modified. Embodiments therefore allow dynamic updating of themenu according to events which occur during the call between the user ofMS A and the user agent operator of the service provider.

In the embodiments described above in relation to FIGS. 16 to 22,configuration data can include positional data defining one or morepositions or locations within touch-screen user interface 504 at whichthe touch-sensitive screen regions should be configured. Theconfiguration data can also include image data relating to theappearance of an icon, for example an icon containing a logo associatedwith the service provider and text data helping clarify what function(s)the icon is associated with.

In the embodiments described above in relation to FIGS. 17 and 18, datacommunications part 406 notifies the call to UA Telephone in steps 17 band 18 b respectively. In alternative embodiments, the call may insteadbe notified to server 100 by one or more network entities located inPSTN B in a similar manner to the notification processes described abovefor network element 108 and SCP 150.

Embodiments involve a service provider system 400 capable ofestablishing a communications session for communication of data withrespect to at least a first telephony user device MS A in a datacommunications network, the system comprising:

a service management part 408 adapted to manage service data for theservice provider;

a service data store 402 adapted to store the service data;

a telephony part ‘UA Telephone’ adapted to conduct a telephone call witha customer of the service provider via the at least first telephony userdevice MS A; and

a data communications part 406 adapted to:

-   -   establish a separate communications session, separate from the        telephone call, for the transfer of data to/from the first        telephony user device, on the basis of one or more call party        details associated with the telephone call; and    -   retrieve service data from the service data store and transmit        data including or derived from the retrieved service data via        the session.

The retrieved service data may be retrieved from data store 402 and dataincluding or derived from the retrieved service data transmitted by thedata communications part in response to establishment of the session.

The data communications part may retrieve and transmit the dataincluding or derived from the service data in response to data input viaa user agent computing device part associated with the user agentoperator conducting the call with the user of MS A.

In embodiments data communications part 406 may modify the retrievedservice data from the service data store before transmittal via thesession. The modification could be carried out on the basis of datainput via the user agent computing device part. Alternatively, or inaddition, the modification could be carried out on the basis of datareceived via the session, for example data received from MS A and/orserver 100.

The data including or derived from the retrieved service data could betransmitted to MS A in the form of predetermined configuration data viathe separate communication session as described above in relation toFIGS. 17 and 18.

The data including or derived from the retrieved service data could betransmitted to MS A in the form of dynamic configuration data via theseparate communication session as described above in relation to FIG.19.

Some exemplary applications of the embodiments described above inrelation to FIGS. 16 to 22 are now given. The exemplary applicationsinvolve a call between a user of MS A and a user agent operator in aservice provider system. A separate communications session isestablished between MS A, data communications part 406 and a user agentcomputing device associated with the user agent operator. The exemplaryapplications also include some exemplary interactions as per item 112depicted in FIG. 19.

In a first exemplary application, the service provider is providing ataxi service and the service provider system has received a call fromthe user of MS A which is distributed to a user agent telephony deviceassociated with the user agent operator accordingly. In suchembodiments, the service provider will typically want to obtain someinformation on the physical location of MS A such that the serviceprovider knows where to send a taxi to meet the user of MS A. In such anembodiment, the service provider has predetermined configuration datawhich, upon establishment of the separate communication session, istransmitted to MS A. The predetermined configuration data instructs MS Ato reconfigure its touch-screen user interface with a touch-sensitivescreen region in an at least first part of the screen.

The touch-sensitive screen region is operable to initiate generation ofgeographical location data associated with the physical location of MS Aand transmit data including or derived from the generated geographicallocation data via the separate communication session. Thetouch-sensitive screen region could for example comprise an icon labeled‘Send location’.

During the call, the user agent operator can thus ask the user of MS Ato press the ‘Send location’ icon which results in the physical locationof MS A being generated and transmitted from MS A to data communicationspart 406. Embodiments thus provide a convenient way for the serviceprovider to obtain the location of the user of MS A without having toask the user for address information verbally over the telephone andalso avoids the user agent operator from having to enter in suchinformation into the service provider system via a user agent computingdevice.

Once the location data is received at the user agent computing device,the user agent operator can process a taxi-booking for the user of MS Abased on the received location data. The user agent operator may requestretrieval of appropriate service data from service provider data store402 by appropriate input via the agent position computing device. Inthis case, the retrieved service data could comprise service dataincluding a taxi number for the booking and also service data associatedwith a live Estimated Time of Arrival (ETA) service for the booked taxi.

The retrieved service data is then modified on the basis of the locationdata received from MS A and transmitted as dynamic configuration data toMS A via the separate communication session. Upon receipt of the dynamicconfiguration data at MS A, the touch-screen user interface of MS A canbe reconfigured accordingly. The reconfiguration may involveconfiguration of a further touch-sensitive screen region in an at leastsecond part of the screen.

The further touch-sensitive screen region could be operable to initiatenavigation via a browser application to a network address (such as an IPaddress or URL) associated with provision of the live ETA service, forexample a network address of data communications part 406. The furthertouch-sensitive screen region could for example comprise an icon labeled‘Press for Live taxi ETA service’.

During the call, the user agent operator can thus ask the user of MS Ato press the ‘Press for Live taxi ETA service’ icon which results in abrowser application on MS A opening a webpage displaying information ona live ETA for their booked taxi.

In a second exemplary application, the service provider is providing arestaurant table booking service and the service provider system hasreceived a call from the user of MS A which is distributed to atelephony user device associated with a user agent operator accordingly.In such embodiments, the service provider will typically want to obtaincontacts details for the user of MS A, for example in order to knowwhich name to book the table under and/or an email address to send atable booking confirmation email to.

In these embodiments, the service provider has predeterminedconfiguration data which, upon establishment of the separatecommunication session, is transmitted to MS A. The predeterminedconfiguration data instructs MS A to reconfigure its touch-screen userinterface with a touch-sensitive screen region in an at least first partof the screen. The touch-sensitive screen region is operable to initiatetransmittal of contact data associated with a user of MS A via saidsession, for example by obtaining such details from address bookapplication data stored on MS A. The touch-sensitive screen region couldfor example comprise an icon labeled ‘Send contact details’ or ‘SendvCard’.

During the call, the user agent operator can thus ask the user of MS Ato press the ‘Send contact details’ icon which results in contactdetails for the user of MS A being transmitted from MS A to datacommunications part 406. Embodiments thus provide a convenient way forthe service provider to obtain the contact details of the user of MS Awithout having to ask the user for the contact details verbally over thetelephone and also avoids the user agent operator from having to enterin such information into the service provider system via a user agentcomputing device.

Once the contact details for the user of MA A are received at the useragent computing device, the user agent operator can process a tablebooking for the user of MS A based on the received contact details. Theuser agent operator may initiate retrieval of appropriate service datafrom service provider data store 402. In this case, the retrievedservice data could comprise service data relating to a representation ofavailable tables in the restaurant at which the user of MS A wishes tobook a table.

The retrieved service data can then be transmitted as dynamicconfiguration data to MS A via the separate communication session. Uponreceipt of the dynamic configuration data at MS A, the touch-screen userinterface of MS A can be reconfigured accordingly. The reconfigurationmay involve configuration of a further touch-sensitive screen region inan at least second part of the screen.

The further touch-sensitive screen region could be operable to initiatenavigation via a browser application to a network address associatedwith provision of a table choosing service, for example a networkaddress of data communications part 406. The further touch-sensitivescreen region could for example comprise an icon labeled ‘Press tochoose your table’.

During the call, the user agent operator can thus ask the user of MS Ato press the ‘Press to choose table’ icon which results in a browserapplication on MS A opening a webpage which allows the user of MS A tosee the layout of the restaurant and select a table of their choosing.

Service providers responsible for processing emergency calls couldemploy a combination of the above two exemplary applications ofembodiments in order to reconfigure a part of the touch-screen userinterface which is operable to initiate transmittal of both geographicallocation data associated with the physical location of MS A and contactdetails such as name, national insurance number etc., to datacommunications part 406. Allowing a user to transmit their location andcontact details to the emergency call processing service provider at theclick of one icon could save valuable time associated with an ambulanceor fire engine reaching the location of an accident or fire.

Customers of a breakdown recovery service provider could similarlybenefit from such functionality.

In a third exemplary application, the service provider is providing aticket purchasing service, for example music concert or cinema tickets,and the service provider system has received a call from the user of MSA which is distributed to a telephony user device associated with a useragent operator accordingly. In such embodiments, the service providerwill typically want to obtain contact details of the user of MS A and apayment for the tickets from the user of MS. In such an embodiment, theservice provider has predetermined configuration data which, uponestablishment of the separate communication session, is transmitted toMS A. The predetermined configuration data instructs MS A to reconfigureits touch-screen user interface with one or more touch-sensitive screenregions in an at least first part of the screen.

One touch-sensitive screen region could comprise an icon labeled Pay fortickets'. The touch-sensitive screen region is operable to initiateprocessing of a transaction from an account associated with a user ofsaid first telephony user device via said session. The region mayextract payment details from a data store of MS A and contact a securepayment server in packet network 106 at which the appropriate funds canbe deducted from the user's credit card or PayPal™ account or suchlike.

Another touch-sensitive screen region could comprise an icon labeled‘Send contact details’, the functioning of which has been describedabove.

During the call, the user agent operator can thus ask the user of MS Ato press the Pay for tickets' which results in payment for the ticketsbeing processed and notified to data communications part 406 and pressthe ‘Send contact details’ which results in contact details for the userof MS A being transmitted from MS A to data communications part 406.Alternatively, a single icon could be configured to provide bothfunctions.

Embodiments thus provide a convenient way for the service provider toobtain the payment and contact details from the user of MS A withouthaving to verbally ask the user for such over the telephone and alsoavoids the user agent operator from having to enter in such informationinto the service provider system via a user agent computing device.

Once the payment has been processed, confirmation of such is notified atthe user agent computing device, and the user agent operator can processposting of the tickets to the user of MS A using an address contained inthe received contact details.

The user agent operator may initiate retrieval of appropriate servicedata from service provider data store 402. In this case, the retrievedservice data could comprise service data relating to the electronictickets for the ticket purchase.

The retrieved service data can then be modified on the basis of thecontact detail data, for example an email address, received from MS Aand transmitted as dynamic configuration data to MS A via the separatecommunication session. Upon receipt of the dynamic configuration data atMS A, the touch-screen user interface of MS A can be reconfiguredaccordingly. The reconfiguration may involve configuration of a furthertouch-sensitive screen region in an at least second part of the screen.

The further touch-sensitive screen region could be operable to initiateemailing of electronic tickets to an email address contained in thecontact details received via the session. The further touch-sensitivescreen region could for example comprise an icon labeled ‘Press to beemailed tickets’.

The further touch-sensitive screen region could be operable to initiatetransmittal via an SMS message of electronic tickets to a phone numbercontained in the contact details received via the session. The furthertouch-sensitive screen region could for example comprise an icon labeled‘Press to receive tickets by SMS’.

The service provider associated with the above described third exemplaryapplication, could also benefit from seat choosing functionality whichallows a customer to select which seats in the appropriate event venuethey would like. The seat choosing functionality could function in asimilar manner as described above in relation to the second exemplaryapplication via transmittal of dynamic configuration data to MS A.Alternatively, the seat choosing functionality could be configured viatransmittal of predetermined configuration data to MS A.

In a fourth exemplary application, the service provider is a retailvendor selling one or more products or services. In such an application,an image of a product the user of MS A is considering purchasing can betransmitted to MS A and displayed on the screen of MS A. Dynamicconfiguration data can be generated by data communications part 406 andtransmitted to MS A in order to reconfigure the touch-screen userinterface of MS A to display a touch-sensitive screen region related tothe purchase of the product in an at least second part of the screen.The further touch-sensitive screen region could for example comprise anicon labeled ‘Buy me’ which can be configured to be embedded into thedisplayed image of the product.

In a fifth exemplary application, the service provider is a retailvendor selling one or more spare part products. The user of MS Atransmits an image of a broken spare part which needs replacing to datacommunications part 406 via the separate communications session. MS Athus requests dynamic configuration data from data communications part406.

The service provider can then select an appropriate part and generatedynamic configuration data to transmit to MS A to reconfigure itstouch-screen user interface to display a ‘Buy me’ icon or suchlike. Thedynamic configuration data may include an image of the spare part whichthe service provider is proposing that the user of MS A purchases,allowing the user of MS A to confirm visually that the spare part is thecorrect spare part.

In a sixth exemplary application, when a user of MS A calls serviceprovider system 400, instead of the call being distributed by ACD 404 toan available user agent operator, the user of MS A is directed to an IVRsystem with the aim of connecting the user to a suitable user agentoperator. Such an Interactive Voice Response (IVR) system could promptthe user of MS A to navigate through a menu system using a series ofdigit key presses on the dialpad, for example “press ‘1’ for technicalsupport, press ‘2’ for billing, etc.” with the user having to wait andlisten for each of the options for each stage of the menu system. SuchIVR systems can be cumbersome and slow to use, so the dynamicreconfiguration functionality of embodiments can be employed to allowthe user to be redirected to a web-based alternative.

In this exemplary application, dynamic configuration data can begenerated by data communications part 406 and transmitted to MS A inorder to reconfigure the touch-screen user interface of MS A to displaya touch-sensitive screen region related to redirection to a webalternative for an IVR in an at least second part of the screen. Thetouch-sensitive screen region could for example comprise an icon labeled‘Go to website alternative of IVR’ icon. The icon is configured, uponuser touch input on the icon, to initiate navigation via a browserapplication to a network address in the data communications network. Thenetwork address in this case directs the user to a web-based alternativeto the standard voice-based IVR system. The web-based alternative allowsa user to read the various options for each stage of the menu systemon-screen and press digits accordingly. Navigation of the menu systemaccording to embodiments will tend to be quicker than the user having towait and listen for each of the options for each stage of a standardvoice-based IVR menu system.

Embodiments involve multi-party conference calls between more than twouser telephony devices. In such embodiments, a separate communicationsession is established between the more than two telephony devicesand/or associated computing devices for the communication of databetween devices associated with all parties of the conference call. Suchembodiments can be implemented by allocation of a conference identifierto a multiparty call, for example by server 100. The conferenceidentifier along with a conference call telephone dialing number can becirculated around the multiple call parties.

In some embodiments, server 100 includes conference call hostingfunctionality, in which case, the conference call telephone dialingnumber may comprise a telephone dialing number associated with aconference call hosting module within server 100. Alternatively, theconference call telephone dialing number may comprise a telephonedialing number associated with a dedicated conference call hostingentity within packet network 106.

Each conference call party will dial the conference call telephonedialing number and enter the conference identifier. The parties willthus be able to conduct a teleconference voice-call.

A separate communication session is then established between the userdevice of each party to the conference call and server 100. Each userdevice will connect to server 100 using a client-server connectionrequest/response procedure. Each user will then enter in the conferenceidentifier which allows server 100 to disambiguate which conference adevice should be connected to. Once each device has established aseparate communication session with server 100, any party to theconference call is able to transmit or receive data with any other partyto the conference call. Data transmitted from one user device will passto server 100 and can be replicated and distributed to other userdevices party to the conference call accordingly by server 100. Server100 may employ multicast techniques, such as IP multicast, toefficiently transfer data to multiple devices.

Capabilities of the various devices to handle receipt/transmission ofconfiguration data according to embodiments can be ascertained bytransmittal of a SIP INFO message with an appropriate eXtensible MarkupLanguage (XML) file embedded within it, with a corresponding SIP OKresponse message being returned containing the capability information.Such SIP INFO messages may be transmitted from automated system 600 toserver 100, from automated system 600 to MS A and/or from server 100 toMS A.

The above embodiments are to be understood as illustrative examples ofembodiments. Further embodiments are envisaged.

In the above-described embodiments, the automated system is a voicemailsystem. In alternative embodiments, the automated system may takedifferent forms.

In another embodiment, the automated system may comprise an interactivevoice response (IVR) unit, with which the user interacts on a call.Configuration data associated with the IVR unit, for example informationresulting from an IVR interaction with the user, may be used to alterthe information displayed on the reconfigured user interface.

In another embodiment, the automated system may comprise a conferencecall system, with which the user interacts on a call. Configuration dataassociated with the conference call system, for example a data entryscreen requesting a conference call ID from the user may be displayedafter the conference call system has been called by the user on ageneral conference calling number and a connection has been made. Theconference call ID may then be collected and transmitted to theconference call system via the separate communications session.

The above described embodiments primarily relate to telephony deviceshaving associated identities in the form of telephone dialing numbers.In other embodiments, one or more, or all of the identities could benon-telephone-dialing-numbers, for example usernames, email addressesetc. Where non-telephone-dialing-number identities are employed,mappings between non-telephone-dialing-number identities and telephonedialing number identities may be stored in data store 102 and used byserver 100 for converting from non-telephone-dialing-number identitiesto telephone dialing numbers after receipt of the call party details

The personal computer PC A described above could alternatively beanother device or combination of devices with corresponding dataprocessing, display and data input capabilities, for example atelevision, a smart television, a general purpose desktop computerterminal, a general purpose laptop computer terminal, a general purposetablet computer terminal, an in-car computing and communications systema satellite navigation system, games console, or any combinationthereof.

In embodiments described above, telephone calls to/from mobile stationsand POTS phones are detected either by application software running onthe mobile stations or by a telephony apparatus configured accordingly.In alternative embodiments, during a voice call, a party to the calluses a computing terminal to enter in call party details (for examplethe calling and called party telephone dialing numbers) for the call viaa web server interface. The web server interface passes the call partydetails to server 100 which can then establish a communications session,separate to the voice call, on the basis of the calling and called partytelephone dialing numbers received from the web server interface.

The logical coupling between user devices for a user may be temporary ormore permanent. If for example a user has a POTS phone and a PC as theiruser devices in their home, then these devices will tend to be used bythe user on a fairly permanent basis, so the logical coupling would tendto be more permanent. If for example a user has a mobile phone and asatellite navigation system in their car, then the logical couplingbetween the two devices may only be valid when the user is in or neartheir car, so the logical coupling would only be maintained temporarilywhen the two devices are within close enough proximity of each other.

The logical coupling between a user's devices can be activated (orotherwise triggered) by a variety of different processes. One examplecould involve communication between a smartphone and a satellitenavigation system via a short wave radio interface (such as a Bluetooth™interface) in order to couple the two devices together locally, alongwith subsequent registration of details of such with server 100. Anotherexample could be registration of device details via a website. A furtherexample might involve registration by a service engineer when installinga telephone and set-top box combination. Alternatively, registrationcould be carried out over the telephone verbally to an administrativeoperator, or via an Interactive Voice Response (IVR) system. The aboveembodiments describe telephone calls and establishment of communicationssessions for user devices of two parties. All embodiments can be appliedto user devices of multiple parties numbering more than two. When themultiple parties are conducting a multi-leg teleconference, acommunications session can be created between all of their user devices,allowing communication of data, not just between two user devices, butbetween many different combinations of user devices, i.e. multi-branchdata communication.

The connections between server 100 and the user devices are describedabove as being HTTP or HTTPS connections. In alternative embodiments,the connections could be peer-to-peer connections such that data iscommunicated between the user devices through a number of peer-to-peernodes. Creating the peer-to-peer connections may involve use ofprocesses for traversing firewalls, for example using protocols such asthe Simple Traversal of User Datagram Protocol (UDP) Through NetworkAddress Translators (NATs) (STUN) protocol.

Further alternatively, the connections could initially be created asHTTP or HTTPS connections between server 100 and the user devices, butthen could be migrated to peer-to-peer connections according to networktopography and/or current network load.

Embodiments described above involve communication of different types ofdata during a communication session, for example software componentidentifiers, software applications, feature identifiers, authorizationrequests, authorization indications, geographical location data, etc.Any of these different types of data may be communicated between thevarious combinations of devices in the above described embodiments,including mobile station to mobile station and mobile station to PC,both with or without use of telephony apparatus for call detection.

Embodiments described above allow a single predetermined affiliate suchas a user of a device or a service provider to be associated withdownload of one or more files by a user of another device. Inalternative embodiments, both a user of a device and a service providercan be associated with download of one or more file by a user of anotherdevice.

The exemplary embodiments described above in relation to FIGS. 20 to 22include reconfiguration of a touch-screen user interface mobiletelephone device MS A. Embodiments can equally be applied to a mobiletelephony device having a non-touch-sensitive screen, in which case thereconfiguration can involve reconfiguring one or more soft-keysaccordingly.

In the above-described embodiments, both call parties transmit, eitherfrom the telephony device, or an associated device, call partyidentifiers for each party to the server 100 in the process of settingup the separate data communications session. These call partyidentifiers are, in the embodiments described, both telephony dialingnumbers (TDNs). In alternative embodiments, one party or both partiesmay be identified by another form of call party identifier, using forexample one or more lookup mechanisms which map a telephony dialingnumber to a different unique identifier and/or vice-versa (examples ofsuch alternatives are described in further detail below.) However, suchlookup mechanisms may increase latency and may introduce unexpectederrors (e.g. if a lookup database such as an address book is not kept upto date.) Hence, whilst it is not indeed necessary for either party totransmit a telephony dialing number of either party (since either partymay be identified by other mechanisms), it is preferred that at leastone of the devices includes the telephony dialing number of the otherparty. Indeed, whilst it is again not necessary, it is preferred thatboth parties transmit the telephony dialing number of the other party,if available, to the server 100, during the session setup. Furthermore,in order at least to reduce latency at the server, and/or to reduce theneed to maintain a separate store of identities and/or to reduce theneed to implement a registration mechanism, it is preferred that bothparties transmit both their own telephony dialing number and thetelephony dialing number of the other party, if available, to the server100, during the session setup. If a call party is identifiable using anadditional identifier, such as an extension number or a conference callID, the additional identifier may be transmitted in association withboth of the telephony dialing numbers, if available, by one or eachparty to the call.

As mentioned above, in alternative embodiments, one, or each, of thecall parties may transmit, either from the telephony device, or anassociated device, a unique identifier in the form other than that of atelephony dialing number which is nonetheless recognizable by the server100. A user device which interacts with the server may thus transmit theunique identifier to identify one party, or both parties, as a party tothe call, instead of a telephony dialing number. For example, the server100 may have access to a data store which includes a set of uniqueidentifiers for all subscribers registered to receive the serviceprovided by the server 100, along with a corresponding telephony dialingnumber for a telephony device associated with each respective uniqueidentifier. Such unique identifiers may be allocated by the server 100during an initial registration procedure, and notified to, and storedby, an application on the user device which interacts with the server100 during the registration procedure. Other globally uniqueidentifiers, such as email addresses, Facebook™ IDs, etc. may be usedalternatively, or in addition, to such allocated unique identifiers.

In embodiments, at least one of the two call parties may use aVoice-over-Internet-Protocol (VoIP) enabled device or other deviceemploying the Session Initiation Protocol (SIP). One, or each, party maybe identified in the call setup procedures by means of a unique SIP useridentifier which may include a telephone dialing number as a useridentifier or a user identifier other than a telephony dialing number,for example a SIP identifier in which the form of username@hostname.Thus, a SIP user identifier can be transmitted to the server 100 as acall party identifier identifying at least one, or each, participant inthe call.

In embodiments, a call party identifier may take the form of an InternetProtocol (IP) address, which may be either a static or dynamicallyallocated IP address. This may for example be the IP address which auser device transmits to the server 100 in a client-server connectionsetup request, for example an HTTP setup request, when establishing aleg of the communications session. This may uniquely identify the callparty associated with the device making the request. If for example, agiven party sends the telephony dialing number of only the other partyto the server 100 in the session setup procedure, then that given partycan nevertheless be identified as a party to the call using the IPaddress of that given party's device used in establishing the sessionleg. The supplied IP address may then be used to send data to that givenparty's device throughout the ensuing communications session, even ifthe IP address is only temporarily allocated to the user device as adynamic IP address. Hence, a static or dynamic IP address may be used,in some embodiments, to identify a call party and may be one of the callparty identifiers which forms part of the call party details transmittedto the server 100, e.g. in a connection setup request during sessionestablishment.

In embodiments, a call party identifier may take the form of a sessionidentifier, or other unique identifier, generated by the server 100 andreceived from the server 100 by a user device in a push notificationmessage. Such a push notification message may be sent from the server inresponse to the server receiving call party details from the other partyto the call, in a first communication session leg. The push notificationmessage is configured, on receipt, to trigger the user device to set upa second communication session leg with the server 100. The user devicemay be configured to include the identifier received in the pushnotification as a call party identifier in a client-server connectionsetup request, for example an HTTP setup request, when establishing thecommunications session leg in response to the push notification message.This may uniquely identify the call party associated with the devicemaking the request, since such identifier may be mapped to the telephonydialing number, or other call party identifier, by the server 100.Hence, an identifier received in a push notification message may beused, in some embodiments, to identify a call party and may be one ofthe call party identifiers which forms part of the call party detailstransmitted to the server 100, e.g. in a connection setup request duringsession establishment.

A unique identifier in any of the various forms described above, in aform other than that of a telephony dialing number, may be used toidentify a given party to the call, in call party details transmitted bya user device associated with that given party. A unique identifier inany of the various forms described, in a form other than that of atelephony dialing number, may in addition, or in the alternative, beused to identify another party to the call, in call party detailstransmitted by that given party. The server 100 may supply the uniqueidentifiers of other parties, using e.g. a synchronization process forpopulating an address book locally stored on the user device with suchidentifiers. Alternatively, such unique identifiers of other parties mayalready be stored by, or manually added by a user of the device, in thelocal address book. Further alternatively, the unique identifiers may bestored in a global address book stored on a remote device. At least oneof the two parties may have a user device which is configured to lookup, from a local data store (e.g. a local address book) or a remote datastore (e.g. a global address book), a correspondence between the otherparty's telephone dialing number, or other received unique identifier,and a different unique identifier. The different unique identifier maythen be used instead to identify the other party to the call in the callparty details transmitted by at least one side of the call to the server100.

In the above, various forms of alternative call party identifiers aredescribed. Whatever form the supplied unique identifier takes, theserver 100 may have a corresponding database and lookup mechanism to mapa supplied unique identifier to a different call party identifier, suchas a telephony dialing number, whereby to match both session legstogether as relating to a particular current telephone call, using theinformation supplied in each respective one of the session legs. Theserver can then bridge the two session legs together, or otherwiseassociate the two session legs, to create a separate communicationssession between the participants in a currently ongoing call.

In the above described embodiments, whilst a different form of callparty identifier may be used in some cases, in a generally accessibletelephony system at least one of the two parties may have no access toidentifying details other than the telephony dialing number of the othercall party when the call is established. Hence, the system may beconfigured such that at least one of the two parties may transmit thecall party identifier of the other party to the server 100 in the formof a telephony dialing number, and that the server 100 is able toprocess one or more call party details in such a form in order toestablish the separate communications session.

In alternative embodiments, rather than both call parties transmittingboth calling party and called party identifiers to identify the partiesto a call, at least one of the parties may transmit only one of the twocall party identifiers to the server 100. This may be done according toa predetermined convention, e.g. a convention which determines that thecalling party should always transmit both identifiers but the calledparty need only transmit one identifier (or vice-versa). Again, theserver 100 is nevertheless able to match both session legs together asrelating to a particular current telephone call, using the informationsupplied in both of the session legs. In this case, it is sufficientthat at least one common call participant, namely that participant whichis determined by convention to be identified by each party to the call,has been identified in each session leg.

In some circumstances, the telephony dialing number, or other call partyidentifier, of the other party may not be received at all during thecall setup procedures. For example, the other party may use a numberwithholding service. Hence, an identifier for the other party may not beavailable to the user device. In this case, the user device may be able,during the setup of the separate communications session, to identifyonly its associated call party (and not the other call party) to theserver 100 as a party to the call. However, providing both sides of thecall do not use a number withholding service, the other party's devicemay be able identify both parties to the call, and may transmit callparty details identifying both call parties to the server 100 duringsession establishment. Again, the server 100 is nevertheless able tomatch both session legs together as relating to a particular currenttelephone call, using the information supplied in both of the sessionlegs. Again, in this case, it is sufficient that at least one commoncall participant, namely the participant not using a number withholdingservice, has been identified in both session legs.

In the above-described embodiments the mobile stations MS A, MS Bcommunicate via a PLMN. Such a PLMN may be any of a variety of differentcellular communications network types, including a 2G network such as aGlobal System for Mobile communications (GSM) network, a 3G network,such as a Universal Mobile Telecommunications System (UMTS) network or a4G network such as a Long Term Evolution (LTE or LTE Advanced) network.Whilst the call setup and call data flow may be conducted via the PLMN,the communications relating to the separate data communications session,e.g. communications with the server 100, may be conducted via adifferent radio access network (RAN), such as a wireless local areanetwork (WLAN) based on the IEEE 802.11 standards.

In the above-described embodiments, the server 100 is described as asingle computing device located in a single network location. However,it should be understood that the server may consist of a distributed setof computing devices or applications, either co-located in a singlenetwork location, or dispersed in different network locations.

It is to be understood that any feature described in relation to any oneembodiment may be used alone, or in combination with other featuresdescribed, and may also be used in combination with one or more featuresof any other of the embodiments, or any combination of any other of theembodiments. Furthermore, equivalents and modifications not describedabove may also be employed without departing from the scope ofembodiments, which is defined in the accompanying claims.

The invention claimed is:
 1. A telephony user device capable ofestablishing a communications session for communication of data withrespect to at least one other device in a data communication network,the telephony user device comprising a processing system configured to:provide a reconfigurable graphical user interface; establish a telephonecall with a service provider; establish a separate communicationssession, separate from the telephone call, for the transfer of datato/from the at least one other device, based on one more call partydetails associated with the telephone call; and reconfigure at least afirst part of the graphical user interface according to configurationdata determined by the service provider and received in the separatecommunication session, wherein the reconfigurable graphical userinterface comprises a touch-screen user interface, wherein thereconfiguration comprises configuring one or more touch-sensitive screenregions in the at least first part which are operable to initiate one ormore operations of the telephony user device in response to user inputvia the one or more touch-sensitive screen regions, and wherein theconfiguration data is predetermined by the service provider prior to thecall.
 2. The telephony user device of claim 1, the processing systembeing configured to receive the configuration data determined by theservice provider in response to establishment of the session.
 3. Thetelephony user device of claim 1, the processing system being configuredto reconfigure at least a second part of the graphical user interfaceaccording to configuration data dynamically determined by the serviceprovider during the call.
 4. The telephony user device of claim 3, theprocessing system being configured to receive the dynamically determinedconfiguration data via the session.
 5. The telephony user device ofclaim 3, wherein the dynamically determined configuration data isreceived in response to a request for the dynamically determinedconfiguration data.
 6. The telephony user device of claim 5, theprocessing system being configured to generate and transmit the requestto the server.
 7. The telephony user device of claim 3, wherein thereconfigurable graphical user interface comprises a touch-screen userinterface, and wherein the reconfiguration comprises configuring one ormore touch-sensitive screen regions in the at least first part and/orthe at least second part which are operable to initiate one or moreoperations of the telephony user device in response to user input viathe one or more touch-sensitive screen regions.
 8. The telephony userdevice of claim 7, wherein the at least first part is reconfigured todisplay one or more touch-sensitive screen regions according to a firstdisplay mode and the at least second part is reconfigured to display oneor more touch-sensitive screen regions according to a second, differentdisplay mode.
 9. The telephony user device of claim 8, wherein thesecond display mode comprises displaying one or more flashing orotherwise dynamically animated touch-sensitive screen regions and thefirst display mode comprises displaying one or more non-flashing orotherwise non-animated touch-sensitive screen regions.
 10. The telephonyuser device of claim 7, wherein one of the one or more touch-sensitiveregions is operable to initiate at least one of: generation ofgeographical location data associated with the physical location of thefirst telephony user device and transmittal of data including or derivedfrom the generated geographical location data via the session; andtransmittal of contact data associated with a user of the firsttelephony device via the session; and processing of a transaction froman account associated with a user of the first telephony user device viathe session; and navigation via a browser application to a networkaddress in the data communications network.
 11. The telephony userdevice of claim 1, wherein the one or more call party details comprise atelephone dialing number.
 12. The telephony user device of claim 1,wherein the one or more call party details comprise a first identityassociated with the telephony user device and a second identityassociated with the at least one other device.
 13. An apparatus adaptedto establish a communications session for communication of data withrespect to a telephony user device having a reconfigurable graphicaluser interface and at least one other device in a data communicationsnetwork, the apparatus comprising a processing system configured to:receive call party details for a telephone call between the telephonyuser device and a service provider; establish a separate communicationssession, separate from the telephone call, for the transfer of datato/from the telephony user device and the at least one other device,based on one or more call party details associated with the telephonecall; and transmit to the telephony user device, via the separatecommunication session, configuration data determined by the serviceprovider, the configuration data being operable to instruct thetelephony user device to reconfigure at least a part of thereconfigurable graphical user interface, wherein the reconfigurablegraphical user interface comprises a touch-screen user interface,wherein the configuration data is operable to instruct the telephonyuser device to configure one or more touch-sensitive screen regions inthe at least first part which are operable to initiate one or moreoperations of the telephony user device in response to user input viathe one or more touch-sensitive screen regions, and wherein theconfiguration data is predetermined by the service provider prior to thecall.
 14. A service provider system capable of establishing acommunications session for communication of data with respect to atleast a first telephony user device in a data communications network,the system comprising: a service management part adapted to manageservice data for the service provider; a service data store adapted tostore the service data; a telephony part adapted to conduct a telephonecall with a customer of the service provider via the at least firsttelephony user device; and a data communications part adapted to:establish a separate communications session, separate from the telephonecall, for the transfer of data to/from the first telephony user device,based on one or more call party details associated with the telephonecall; and retrieve service data from the service data store and transmitdata including or derived from the retrieved service data via the,session, wherein the first telephony user device comprises areconfigurable graphical user interface having a touch-screen userinterface, wherein the data including or derived from the retrievedservice data which is transmitted via the session comprisesconfiguration data which is operable to instruct the telephony userdevice to configure one or more touch-sensitive screen regions which areoperable to initiate one or more operations of the telephony user devicein response to user input via the one or more touch-sensitive screenregions, and wherein the configuration data is predetermined by theservice provider prior to the call.
 15. The service provider system ofclaim 14, wherein the data communications part is adapted to: retrieveand transmit the data including or derived from the service data inresponse to establishment of the session; or retrieve and transmit thedata including or derived from the service data in response to datainput via a user agent computing device part of the system; and/ormodify the retrieved service data from the service data store before thetransmittal via the session.
 16. The service provider system of claim15, wherein the modification is carried out on the basis of: data inputvia a user agent computing device part of the system; or data receivedvia the session.
 17. The service provider system of claim 14, whereinthe one or more call party details comprise a first identity associatedwith the first telephony user device and a second identity associatedwith the telephony part.
 18. The service provider system of claim 14,wherein the service provider system comprises a call center having acall distributing system capable of distributing incoming telephonecalls to one or more call center operators, the incoming telephone callsbeing distributed according to the availability of the one or more callcenter operators, and wherein the telephone call comprises an incomingcall distributed to an operator of the telephony part by the call centercall distributing system.
 19. A computer program product comprising anon-transitory computer-readable storage medium having computer readableinstructions stored thereon, the computer readable instructions beingexecutable by a computerized device to cause the computerized device tooperate a telephony device capable of establishing a communicationssession for communication of data with respect to at least one otherdevice in a data communications network, the telephony user devicecomprising a processing system configured to: provided a reconfigurablegraphical user interface; establish a telephone call with a serviceprovider; establish a separate communications session, separate from thetelephone call, for the transfer of data to/from the at least one otherdevice, based on one or more call party details associated with thetelephone call; and reconfigure at least a first part of the graphicaluser interface according to configuration data determined by the serviceprovider and received in the separate communication session, wherein thereconfigurable graphical user interface comprises a touch-screen userinterface, wherein the reconfigurable comprises configuring one or moretouch-sensitive screen regions in the at least first part which areoperable to initiate one or more operations of the telephony user devicein response to user input via the one or more touch-sensitive screenregions, and wherein the configuration data is predetermined by theservice provider prior to the call.
 20. A telephony user device capableof establishing a communications session for communication of data withrespect to at least one other device in a data communications network,the telephony user device comprising a processing system configured to:provide a reconfigurable graphical user interface; establish a telephonecall with a service provider; establish a separate communicationssession, separate from the telephone call, for the transfer of datato/from the at least one other device, based on one or more call partydetails associated with the telephone call; reconfigure at least a firstpart of the graphical user interface according to configuration datadetermined by the service provider and received in the separatecommunication session, wherein the reconfigurable graphical userinterface comprises a touch-screen user interface, and wherein thereconfiguration comprises configuring one or more touch-sensitive screenregions in the at least first part which are operable to initiate one ormore operations of the telephony user device in response to user inputvia the one or more touch-sensitive screen regions; and reconfigure atleast a second part of the graphical user interface according toconfiguration data dynamically determined by the service provider duringthe call.